Closed shawmanz32na closed 4 years ago
@shawmanz32na are you using proxy or similar to access the internet? If so, please configure it: https://docs.docker.com/docker-for-windows/#proxies
@friism Our company definitely has quite a network setup, so I don't doubt that there are a few proxies in there somewhere. However, I've never had to configure any other applications to use a proxy, and as mentioned, I can access https://registry-1.docker.io/v2 from a browser with no problems. Additionally, I had my co-worker next to me (on mac) install docker and run the hello-world container, and his attempt went swimmingly.
I found the problem.
I had a statically-configured network adapter that used various 10.x.x.x subnets. Disabling this interface allows docker to connect. Changing the Docker NAT address to 172.16.x.x and 192.168.1.x does not resolve the problem.
Does anyone have any details about how to configure Docker to not struggle when paired with another 10.x.x.x addressing scheme?
@shawmanz32na
I got a same error response. But I was using Docker in my home laptop (e.g. no complicated network settings). I tried manually setting the DNS then Docker magically worked. Maybe you can give it a try.
Go to Docker settings
GUI then Network
then set the DNS Server
to Fixed: 8.8.8.8
. Then restart Docker.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
comment.
Stale issues will be closed after an additional 30d of inactivity.
Prevent issues from auto-closing with an /lifecycle frozen
comment.
If this issue is safe to close now please do so.
Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. /lifecycle stale
I'm satisfied that this issue was a configuration problem on my end, and not a Docker issue that needs to be fixed. However, I have not seen anywhere in the documentation that notes that Docker for Windows is incompatible when run on machines statically configured with 10.x.x.x networks.
If someone can point me to that documentation, or add that documentation, I'll happily close this issue.
Closed issues are locked after 30 days of inactivity. This helps our team focus on active issues.
If you have found a problem that seems similar to this, please open a new issue.
Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. /lifecycle locked
Expected behavior
Docker connects to the docker registry and downloads the required hello world image
Actual behavior
docker run hello-world
fails with an error messageInformation
I can navigate to registry-1.docker.io from my web browser, but when using the docker utility, the requests time out.
Diagnostic ID B14F35E1-BD1E-4E58-9B2B-50EF138BF20A/2017-03-09_13-23-48
Steps to reproduce the behavior
docker run hello-world