No network connectivity in some docker containers after upgrade to 1153.0.0 #1554
After upgrading from stable (1068.10.0) to alpha (1153.0.0), some freshly submitted fleet services start containers that do not have network connectivity. From within the container I cannot ping the docker bridge (default gateway address) or any other containers or host interfaces. A simple "docker restart " resolves the issue.
QEMU/KVM on Openstack
All docker containers have network connectivity, as it has always been in the past.
A few containers cannot reach any hosts, not even able to ping the default gateway (docker0).
This happens across different docker images that are based on different distributions, so I don't think it is related to the image.
I'm passing these options to docker:
The text was updated successfully, but these errors were encountered:
I have the same issue docker doesn't attach veth interface to docker0 bridge. Restarting daemon helps and manually attaching interface by running
This is what I have observed so far from trying to test and narrow it down to a problematic component: Docker containers' network links randomly fail to have their master set. This happens with Docker in CoreOS alpha and beta. The
It continues to fail when booting a kernel from stable and the user space from alpha or beta. It does not fail with alpha or beta kernels and stable user spaces.
It fails whether Docker is built with Go 1.6 or 1.7. It fails with all Project Atomic patches applied.
It fails when patching libnetwork to just use an
I'll add that we're experiencing the same issue using CoreOS Beta (1153.4.0) running in AWS:
I used a container that simply
I believe I have a (rather unfortunate) workaround for people who can't run a patched Docker: stop/mask