moby: Get https://registry-1.docker.io/v2/: dial tcp [::1]:443: getsockopt: connection refused.

The problem

Right after upgrading from to Docker version 17.03.0-ce, build 60ccb22, when launching the following command:

docker run hello-world

I get the following error message:

Unable to find image 'hello-world:latest' locally
docker: Error response from daemon: Get https://registry-1.docker.io/v2/: dial tcp [::1]:443: getsockopt: connection refused.
See 'docker run --help'.

When going from my browser to https://registry-1.docker.io/v2/, I also get the following response:

{
  errors: [
    {
      code: "UNAUTHORIZED",
      message: "authentication required",
      detail: null
    }
  ]
}

What I tried to solve it

I tried to reset the application to factory defaults, and I also deleted the ~/.docker folder. Didn’t work out.

OS

macOS Sierra: 10.12.3

About this issue

  • Original URL
  • State: closed
  • Created 7 years ago
  • Reactions: 6
  • Comments: 22 (5 by maintainers)

Commits related to this issue

Most upvoted comments

I had the same issue on Windows 10. Restart of docker fixed the issue.

restarting the Docker client solves the problem for Win10.

Yes!!!

What did it

We had a custom dns resolver for our docker domains. Removing the file I had in /etc/resolver/docker did it.

Thanks a lot for your help!

As for me, this issue can be closed.

Please reopen. I have same issue on Windows 10 with hyper-v. Why we should restart docker all the time due to bugs?

λ docker --version
Docker version 17.06.2-ce, build cec0b72
λ docker-compose --version
docker-compose version 1.14.0, build c7bdf9e3
λ docker-machine --version
docker-machine version 0.12.2, build 9371605

Yeah~Restart docker on Windows 10 and fixed the same issue. Thanks @sthristov

I have the same issue on Windows 10. Any help is appreciated. Hers Diagnostic id: 67A5CFBF-8C9B-4CEC-8287-DEACBF749C45/2017-05-02_15-17-29

Thanks very much for the quick confirmation!

Here’s one from my machine: 047491C5-BD95-4CF5-B142-C30F080EE1C7

What I tried to solve it

I additionally restarted macOS in the meantime.

Gladly.

Diagnostic ID: 31D2736A-3D88-4E06-BF06-5E0D246A9197