takeout: Connection refused trying to connect to registry-1.docker.io
I know I’m a Takeout maintainer so I don’t have to make this public, but I figure I’m not the only person who’ll ever see this error, so I’ll put it here publicly while I try to figure it out.

ERR Error response from daemon: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 192.168.64.1:53: read udp 192.168.64.2:36267->192.168.64.1:53: read: connection refused
This is on an m1 laptop using the brand new Docker for desktop build, so first thing I’m going to do is install a Docker container the classic way not using takeout and I bet I’ll have the same issue there. 😃
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 16 (8 by maintainers)
I faced this error when running Docker Engine using colima on Mac
Just after restarting colima, by executing command:
colima restart, I was able to push my Docker image on the DockerHub.user$ docker run hello-world Unable to find image ‘hello-world:latest’ locally docker: Error response from daemon: Get “https://registry-1.docker.io/v2/”: dial tcp 54.236.113.205:443: connect: connection refused. user$ curl https://registry-1.docker.io/v2/ {“errors”:[{“code”:“UNAUTHORIZED”,“message”:“authentication required”,“detail”:null}]}
what might be the issue ?
Thanks again @jasonvarga!
For anyone else who runs into this, this is a Docker for Mac + DNSMasq (likely installed by Laravel Valet) thing, not a Takeout thing.
https://github.com/docker/for-mac/issues/5186
@hcancelik You’re right! I had tried to restart it in the preferences, using “apply and restart” on some changes I was making, but that apparently didn’t cut it; I actually had to click on the dropdown and click Restart, and then that fixed it.
Thanks!
@mattstauffer try stopping the dnsmasq service