Docker Community Forums

Share and learn in the Docker community.

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)

docker
dockerhub

(Ackris) #1

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:

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

Yet 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


(Goffinf) #2

The docker daemon uses its own http proxy settings. You can see what they are using

docker info

HTHs

Fraser.


(Ackris) #3

We went ahead with docker save and load option. Our organization’s proxy was not allowing connection with docker hub

Regards
Aditya


(Goffinf) #4

That’s going to be a bit limiting. Even if you are using docker save and load you have to be able to get a base image from somewhere in the first place, which if you are getting outside of your corporate controls somewhat defeats their purpose and introduces risk not least from lack of visibility.
Anyway, I guess that’s a discussion you need to have with your security and network guys.