Cannot connect from Docker containers to the outside #1936
Comments
@pietervisser I guess you are running the above command in a while loop. Can you please check if you can reproduce the same issue with unique network names (e.g. |
@lucab, thanks but no I'm not running it in a while loop. Executing this just a couple of times manually will result in connection issues. To be sure, I used unique networks and can still reproduce this issue. Use could use this loop to reproduce the issue.
|
we also experience the same thing on AWS. re-running ping multiple times (inside a user create network container) sometimes work and sometimes not. i don't have to re-create the network.. this update screwed up an ~40 nodes nomadproject cluster for us. |
Can you try this and see if it makes a difference? Copy |
@dm0- seems like it does make a difference, but I had to reboot for this to work. |
We'll build a new stable with that fix which should be released over the next day. |
To clarify the actual issue: this is basically a redux of #1554, but for the bridge interfaces I'm not sure the exact root cause. I can't reproduce this on the old stable and the docker version there was identical. We'll add a test for Thanks for reporting. |
I am experiencing network problems with the current version 1353.7.0 which did not occur before (at least not before 1353.6.0, I am not sure when this happened first). I use When the coreos server is restarted (or the networks are removed), the apps are accessible from the outside when using |
Issue Report
Bug
Since the update to 1353.6.0 we experience network issues when trying to ping from a docker container to the outside.
Container Linux Version
Environment
Google Cloud
Expected Behavior
Pinging to 8.8.8.8 from a Docker container in a docker network should result in no pakket loss.
Actual Behavior
When creating a new docker network and trying to connect to the world, sometimes a network is created in which no connections are possible to the outside.
Repeat this several times, and sometimes 100% packet loss.
docker network create foo > /dev/null; docker run --rm --net foo busybox ping -c 1 -w 1 -q 8.8.8.8; docker network rm foo > /dev/null
The text was updated successfully, but these errors were encountered: