moby: ERROR: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:59801->[::1]:53: read: connection refused


BUG REPORT INFORMATION

Description I just installed Docker CE yesterday and now I loaded a couple of images and now would like to login using docker login and whenever I type in my username and password this error shows up ERROR: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:59801->[::1]:53: read: connection refused. I am using Windows 10, by the way.

Steps to reproduce the issue:

  1. Open Command Prompt
  2. type in docker login
  3. enter username and password

Describe the results you received: Result received was ERROR: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:59801->[::1]:53: read: connection refused

Describe the results you expected: Result expected is Login Succeeded

Additional information you deem important (e.g. issue happens only occasionally):

Output of docker version:

Client:
Version:      17.06.0-ce
API version:  1.30
Go version:   go1.8.3
Git commit:   02c1d87
Built:        Fri Jun 23 21:30:30 2017
OS/Arch:      windows/amd64
Server:
Version:      17.06.0-ce
API version:  1.30 (minimum version 1.12)
Go version:   go1.8.3
Git commit:   02c1d87
Built:        Fri Jun 23 21:51:55 2017
OS/Arch:      linux/amd64
Experimental: true

Output of docker info:

Containers: 0
Running: 0
Paused: 0
Stopped: 0
Images: 14
Server Version: 17.06.0-ce
Storage Driver: overlay2
Backing Filesystem: exfs
Supports d_type: true
Native Overlay Diff: true
Logging Driver: json-file                                                                                                                                                                                                                    Cgroup Driver: cgroupfs
Plugin:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: cfb82a876ecc11b5ca0977d1733adbe58599088a
runc version: 2d41c047c83e09a6d61d464906feb2a2f3c52aa4
init version: 949e6fa
Security Options: 
seccomp
Profile: default
Kernel Version: 4.9.31-moby
Operating System: Alpine Linux v3.5
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 1.934GiB
Name: moby
ID: 3WOY:UFSW:LDOT:AXVM:SAZZ:MFPD:MTJC:YXUJ:A3EM:WBKH:2S7T:MXFZ
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
File Descriptors: 15
Goroutines: 24
System Time: 2017-07-05T02:22:56.0832539Z
EventsListeners: 0
Registry: https://index.docker.io/v1/
Experimental: true
Insecure Registries: 
127.0.0.0/8
Live Restore Enabled: false

About this issue

  • Original URL
  • State: closed
  • Created 7 years ago
  • Comments: 17 (3 by maintainers)

Most upvoted comments

I had the same problem. Try to reload the docker, it helped me.

Same error I am also facing. Using Win10 Enterprise. The issue is 100% similar to the above(docker version is exactly similar). The error message I am getting after supplying the username and password for docker login command is: Error response from daemon: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:33937->[::1]:53: read: connection refused

docker pull command also fails with same error.

Same as @TooFeD - restarting Docker corrected the problem for me.

To add more reliability to the answers by @TooFeD and @jongalloway, restarting Docker helped solving my problem, too.

Looks like this is a Docker for Windows / Docker for Mac issue; and IIRC, should be resolved if a DNS (e.g.8.8.8.8) is configured explicitly, see https://github.com/docker/for-mac/issues/1317, and other issues in https://github.com/docker/for-win/issues?utf8=✓&q=is%3Aissue+read+udp, and https://github.com/docker/for-mac/issues?utf8=✓&q=is%3Aissue+read+udp

If you are behind a proxy you should change the docker daemon config as the documentation indicates