Docker registry error response from daemon i/o timeout

10,833

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.

Share:
10,833
Twoez
Author by

Twoez

I do have a passion for programming. My main focus is web development. I am a beginner level programmer, but willing to learn everyday and not scared of failure.

Updated on June 14, 2022

Comments

  • Twoez
    Twoez about 2 years

    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?