New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

coreos in coreos docker0 is down #2501

Open
netboy88 opened this Issue Sep 9, 2018 · 4 comments

Comments

Projects
None yet
2 participants
@netboy88

netboy88 commented Sep 9, 2018

Issue Report

coreos in coreos
2: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 02:42:29:43:27:71 brd ff:ff:ff:ff:ff:ff
inet 172.18.0.1/16 brd 172.18.255.255 scope global docker0
valid_lft forever preferred_lft forever

[ 1695.787018] IPv6: ADDRCONF(NETDEV_UP): docker0: link is not ready

Bug

Container Linux Version

$ cat /etc/os-release
NAME="Container Linux by CoreOS"
...NAME="Container Linux by CoreOS"
ID=coreos
VERSION=1800.7.0
VERSION_ID=1800.7.0
BUILD_ID=2018-08-15-2254
PRETTY_NAME="Container Linux by CoreOS 1800.7.0 (Rhyolite)"
ANSI_COLOR="38;5;75"
HOME_URL="https://coreos.com/"
BUG_REPORT_URL="https://issues.coreos.com"
COREOS_BOARD="amd64-usr"
BUG_REPORT_URL="https://issues.coreos.com"

Environment

What hardware/cloud provider/hypervisor is being used to run Container Linux?

Expected Behavior

Actual Behavior

Reproduction Steps

  1. ...
  2. ...

Other Information

@bgilbert

This comment has been minimized.

Show comment
Hide comment
@bgilbert

bgilbert Sep 12, 2018

Member

Hi @netboy88, could you provide the information requested above? Otherwise there's not enough here for us to act on.

Member

bgilbert commented Sep 12, 2018

Hi @netboy88, could you provide the information requested above? Otherwise there's not enough here for us to act on.

@netboy88

This comment has been minimized.

Show comment
Hide comment
@netboy88

netboy88 Sep 13, 2018

@bgilbert I build coreos docker image use https://github.com/steigr/coreos-builder
Container Linux is runing hardware or virtualbox
1、 journalctl -b | grep bridge
Aug 30 19:52:49 localhost kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Is this normal?
2、docker exec -it 1keyoscoreos sysctl -a | grep disable_ipv6
net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.br-0.disable_ipv6 = 0
net.ipv6.conf.default.disable_ipv6 = 1
net.ipv6.conf.docker0.disable_ipv6 = 0
net.ipv6.conf.eth0.disable_ipv6 = 1
net.ipv6.conf.lo.disable_ipv6 = 1
net.ipv6.conf.vethd7c0557.disable_ipv6 = 0
why net.ipv6.conf.docker0.disable_ipv6 = 0

2、but i run docker run --name dind -d --privileged docker:dind
dind is run ok!

all runing in coreos 1897.0.0 is same

you run coreos in coreos is ok?

Thanks!

netboy88 commented Sep 13, 2018

@bgilbert I build coreos docker image use https://github.com/steigr/coreos-builder
Container Linux is runing hardware or virtualbox
1、 journalctl -b | grep bridge
Aug 30 19:52:49 localhost kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Is this normal?
2、docker exec -it 1keyoscoreos sysctl -a | grep disable_ipv6
net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.br-0.disable_ipv6 = 0
net.ipv6.conf.default.disable_ipv6 = 1
net.ipv6.conf.docker0.disable_ipv6 = 0
net.ipv6.conf.eth0.disable_ipv6 = 1
net.ipv6.conf.lo.disable_ipv6 = 1
net.ipv6.conf.vethd7c0557.disable_ipv6 = 0
why net.ipv6.conf.docker0.disable_ipv6 = 0

2、but i run docker run --name dind -d --privileged docker:dind
dind is run ok!

all runing in coreos 1897.0.0 is same

you run coreos in coreos is ok?

Thanks!

@bgilbert

This comment has been minimized.

Show comment
Hide comment
@bgilbert

bgilbert Sep 13, 2018

Member

@netboy88 Thanks for the additional information. What behavior did you expect, and what happened instead?

Member

bgilbert commented Sep 13, 2018

@netboy88 Thanks for the additional information. What behavior did you expect, and what happened instead?

@netboy88

This comment has been minimized.

Show comment
Hide comment
@netboy88

netboy88 Sep 14, 2018

@bgilbert
1、 docker run --name 1keyoscoreos -d --privileged 117.25.155.104:5000/port/1keyos
port/1keyos is build https://github.com/steigr/coreos-builder
2、docker exec -it 1keyoscoreos ip addr show docker0
2: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 02:42:22:2c:75:9b brd ff:ff:ff:ff:ff:ff
inet 172.18.0.1/16 brd 172.18.255.255 scope global docker0
valid_lft forever preferred_lft forever
docker0 is NO-CARRIER and DOWN
3、docker exec -it 1keyoscoreos docker run -it busybox
ping in busybox in is not accessible
4、docker exec -it 1keyoscoreos ip addr show docker0
2: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 02:42:22:2c:75:9b brd ff:ff:ff:ff:ff:ff
inet6 fe80::42:22ff:fe2c:759b/64 scope link
valid_lft forever preferred_lft forever
docker0 ipv4 does not exist. why?
Thanks!

netboy88 commented Sep 14, 2018

@bgilbert
1、 docker run --name 1keyoscoreos -d --privileged 117.25.155.104:5000/port/1keyos
port/1keyos is build https://github.com/steigr/coreos-builder
2、docker exec -it 1keyoscoreos ip addr show docker0
2: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 02:42:22:2c:75:9b brd ff:ff:ff:ff:ff:ff
inet 172.18.0.1/16 brd 172.18.255.255 scope global docker0
valid_lft forever preferred_lft forever
docker0 is NO-CARRIER and DOWN
3、docker exec -it 1keyoscoreos docker run -it busybox
ping in busybox in is not accessible
4、docker exec -it 1keyoscoreos ip addr show docker0
2: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 02:42:22:2c:75:9b brd ff:ff:ff:ff:ff:ff
inet6 fe80::42:22ff:fe2c:759b/64 scope link
valid_lft forever preferred_lft forever
docker0 ipv4 does not exist. why?
Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment