-
Notifications
You must be signed in to change notification settings - Fork 291
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
Docker cannot download images #1581
Comments
We get the same problem. Can you check your log if you also get these errors from vpnkit? Might be related to #1238.
This is on a fresh installation of docker. I also cannot pull any image, so docker is basically non-operational. |
Sure, how do I pull the logs ? |
You can access them on the same settings page as the diagnostics: But I believe this to be a bug in Docker now. I just switched to the (actually older) edge version of Docker and now I can pull images. If I go back to "stable" again, it does not work anymore. |
Switching to Edge didn't work for me. My logs says this:
So I guess its the same error |
Yep. I get error too. How fix this? UPD: i install Nightly build, and all work fine. |
For me it was the Edge build that worked. I can finally pull images, thanks for your comment @msgeissler . |
Fixed in the latest Edge version 1.8 |
Closed issues are locked after 30 days of inactivity. 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. |
I installed Docker for Win Stable and ran "docker run hello-world"
Expected behavior
Docker hellow world image should be downloaded
Actual behavior
The following error message is displayed:
docker: Error response from daemon: Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers).
Information
Docker installed Hyper-V
No VPN Software installed
Firewalls are all of
Windows 10 Pro 15063.850
Diagnostic ID: 7F5738A1-A330-4056-9DD2-72CE5287C3F0/2018-01-18_22-04-39
Steps to reproduce the behavior
The text was updated successfully, but these errors were encountered: