You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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
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.
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
The text was updated successfully, but these errors were encountered:
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
By browsing multiple forums we have done the following:
/etc/resolv.conf
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
The text was updated successfully, but these errors were encountered: