Reputation: 548
Error response from daemon: Get https://registry.xxx.com:5000/v1/users/: dial tcp: lookup registry.xxx.com on 192.168.65.1:53: read udp 192.168.65.2:42307->192.168.65.1:53: i/o timeout
I have set up a private docker registry running on an Ubuntu server, but keep getting the error above when I do "docker login https://registry.xxx.com:5000".
When I run "curl -v https://registry.xxx.com:5000" from my mobile phone's network I can resolve the host and am able to login to the registry succesfully. But I cannot do this and get a "cannot resolve host" error when running "curl -v https://registry.xxx.com:5000 from the same network the registry is on".
It seems that it can't resolve the domain. I have a draytek router.
Any ideas?
Upvotes: 10
Views: 25488
Reputation: 761
I've solved the issue by login with my docker id.
By default, my docker logged out. I go unnoticed. After logging into Docker, everything is running smoothly.
Upvotes: 1
Reputation: 1
I have solved the same issue by resetting the router dns cache, I suggest to try it.
Upvotes: 0
Reputation: 31
Go to: Docker App -> Settings -> Resource -> Network -> DNS Server and set IP again.
I encounter this problem while I am at the company. no problem when at home.
I think it is the problem of the firewall in the company
Upvotes: 3
Reputation: 935
I've solved the exact same issue by force-ending the VBoxHeadless.exe process in the task manager.
Upvotes: 0
Reputation: 133
Even though this problem was solved by a router change, I'm hit by the "read udp ... timeout" problem every other day. The bug is discussed in docker forums and is apparently related to a DNS lookup. I've found a work-around by doing a docker-machine restart.
Upvotes: 11
Reputation: 548
Problem solved I had the registry.domain.com DNS-forwarded in the Draytek router, oops ;)
Upvotes: 0