Kitematic: (HTTP code 500) server error - {"message":"Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:33405->[::1]:53: read: connection refused"}

[j1mbosharp]

Expected behavior

Actual behavior

Information about the Issue

Steps to reproduce the behavior

1. ...
2. ...

[j1mbosharp]

Trying t images.o load LAMP from tutum using Kitematic. Same error for other

[FrenchBen]

Are you behind a firewall or VPN?
See our wiki for possible solutions:
https://github.com/docker/kitematic/wiki/Common-Proxy-Issues-&-Fixes

[alankent]

I just got a new laptop, setting it all up. I got this problem when trying Kitematic out too. I don't have a proxy. The problem turned out to be Docker Engine failing to download images (not Kitematic). Running docker commands to download images from the command line was also failing (it just hung). Being on Windows I did a reboot ... and that cleared the problem - everything worked fine after that. So I suspect this error message is an indication of a docker engine problem downloading images, not a Kitematic problem.

The message I got was:

(HTTP code 500) server error - {"message":"Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:35914->[::1]:53: read: connection refused"}

Not a very friendly Kitematic error message!

[FrenchBen]

Kitematic doesn't try to assume anything and thus sends the same error that the engine would (API response)
@alankent what would've been a better message?

[zephraph]

Just to throw this out there, I ran across the same error. From the message it seems like there's a network issue.

(HTTP code 500) server error - {"message":"Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:50169->[::1]:53: read: connection refused"}

I suspect that's not actually what's happening. I'm not behind a proxy, firewall isn't blocking. I'll dig around a bit.

[FrenchBen]

@zephraph Are you using toolbox or Docker for Mac?
What happens when you do docker run hello-world what happens when you do the same within the VM (if on Toolbox)

[zephraph]

I apologize for not putting in the specifics. I encountered that on my windows machine. When I tried to do a docker run it just hung there for a while. I had to manually kill it.

I’ll report back tonight on more detailed specifics like docker version, system specs, etc. Seems to be a windows specific issue.

[fredhohenstein]

==

I apologize for not putting in the specifics. I encountered that on my windows machine. When I tried to do a docker run it just hung there for a while. I had to manually kill it.

I have the same issue. Have to restart de docker components (from the windows tray icon) and then sometimes it works. I'll restart the docker components (from the windows tray icon) until it works...

[aliamani]

resolve with chage dns nameserver in:
vim /etc/resolv.conf

nameserver 8.8.8.8

[salmagomaa]

sudo vi /etc/resolv.conf

nameserver 8.8.8.8
nameserver 8.8.4.4