Skip to content
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

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) #37532

Closed
ackris opened this issue Jul 26, 2018 · 1 comment

Comments

@ackris
Copy link

ackris commented Jul 26, 2018

Hi

I am getting 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) while trying to pull images. As a heads up, we are using Docker EE inside a secured zone.

Operating System: Red hat 7.4 (maipo)
uname -r: 3.10.0-693.5.2.el7.x86_64

Client: Docker Enterprise Edition (EE) 2.0
 Version:       17.06.2-ee-10
 API version:   1.30
 Go version:    go1.8.7
 Git commit:    66261a0
 Built: Fri Apr 27 00:38:41 2018
 OS/Arch:       linux/amd64

Server: Docker Enterprise Edition (EE) 2.0
 Engine:
  Version:      17.06.2-ee-10
  API version:  1.30 (minimum version 1.12)
  Go version:   go1.8.7
  Git commit:   66261a0
  Built:        Fri Apr 27 00:40:03 2018
  OS/Arch:      linux/amd64
  Experimental: false

By browsing multiple forums we have done the following:

  1. We have inserted Google's DNS servers in /etc/resolv.conf
  2. We have configured proxy settings of our organization according to the suggestion from Docker Documentation.
  3. We have rebooted the server.
  4. We have created a docker hub account. Even this is getting timed out when access our account from docker client using docker login.

But we are unable to pull or execute any docker commands which need external access. I don't know where the problem lies. So, we are requesting docker community's guidance on this issue.

Thanks and Regards
Aditya

@ackris
Copy link
Author

ackris commented Jul 30, 2018

As mentioned in the referenced issue, this problem was resolved by saving and loading the docker images. Just ensure the requisite ports are opened.

@ackris ackris closed this as completed Jul 30, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants