Docker network problem with Linode
yum install docker
chkconfig docker on
service docker start
docker run -i -t fedora /bin/bash
- inside the Docker container:
[root@c9f79f5d018b /]# curl
curl: (56) Recv failure: Connection reset by peer
[root@c9f79f5d018b /]# ping -c2 linode.com
PING linode.com (22.214.171.124) 56(84) bytes of data.
64 bytes from www-loadbal2.linode.com (126.96.36.199): icmp_seq=1 ttl=52 time=43.9 ms
64 bytes from www-loadbal2.linode.com (188.8.131.52): icmp_seq=2 ttl=52 time=43.9 ms
Ping works, but no tcp connections. curl to other hosts results in same result. Can't run yum (times out).
Same process tried for Ubuntu 10.04 LTS and Debian 7 as base distros, same problem each time.
Linode support has been trying to help, but no answers so far. They've tried it themselves and it works fine for them. They have also migrated machine to a different host. Same result.
I'm out of ideas. Anyone?
Anyway, make sure you try reaching web sites that you know aren't connected to Linode's load balancers.
[root@7961df4985e3 /]# yum update
Loaded plugins: fastestmirror
Could not retrieve mirrorlist
12: Timeout on
Can you please provide the ticket ID? I'd like to take a look at this ticket and hopefully shine some light on this issue.
After further investigation, we have determined that this is an issue with the physical server that the Linode was on. We have forwarded this to our administrators and our Hardware Team so that this issue can be resolved. We do not have an ETA for the time that it will take for us to resolve the issue, as the issue is present only on a specific server build.
This being said, this issue will not happen across all physical servers, but only specific ones. In the event someone else experiences this issue, they should reach out to us via ticket so that we can look into this issue for them.
We appreciate your patience and understanding.
Dave Russell Jr
Linode Support Specialist.
Just want to chime in from Docker Inc, that we too were experiencing this problem and in working with the Linode team have confirmed that their fix indeed resolves the issue.