Docker Hub : Unable to pull container: "connection reset by peer"

Docker Hub
,
1

Hi !

When I try to pull a container, I get an error “connection reset by peer”

 docker pull hello-world
Using default tag: latest
Error response from daemon: Head "https://registry-1.docker.io/v2/library/hello-world/manifests/latest": read tcp 172.16.2.100:53842->54.198.86.24:443: read: connection reset by peer

When I curl the https://registry-1.docker.io/v2/library/hello-world/manifests/latest , I get UNAUTHORIZED error :

 curl https://registry-1.docker.io/v2/library/hello-world/manifests/latest
{"errors":[{"code":"UNAUTHORIZED","message":"authentication required","detail":[{"Type":"repository","Class":"","Name":"library/hello-world","Action":"pull"}]}]}

When I search on Docker It works, so I don’t think this a network issue or a least not fully…

 docker search hello-world
NAME                                       DESCRIPTION                                     STARS     OFFICIAL
hello-world                                Hello World! (an example of minimal Dockeriz…   2201      [OK]
rancher/hello-world                        This container image is no longer maintained…   6
okteto/hello-world                                                                         0
tutum/hello-world                          Image to test docker deployments. Has Apache…   90

I’ve already lost 2 day on this issue. And I have seen a lot of message “connection reset by peer” on many forum. (also china one…)
Also, I cannot try the solution to use an alternative Internet connection to change my public IP…

Does some one found the reason of this error, and a true solution ?
Thanks a lot . I think we sjould link together all those post about this issue…

Christophe

2

Hi !
I close the subject.
There was a misconfiguration on HyperV.
Thanks.
Christophe

3

Hi could you go into more detail on how you fixed this issue? I’m currently facing the same thing.
Thank you!

4

Hi,
The issue was on the HyperV network configuration.
I don’t have much details because it’s not me who manage HyperV Server.
Christophe