Docker Community Forums

Share and learn in the Docker community.

Error response from daemon: Get https://registery.aquasec.com/v2/: dial tcp: lookup registery.aquasec.com

When I try to login to image directory, I get “Error response from daemon: Get dial tcp: lookup registery.aquasec.om on 10.13.60.1:53: no such host” response.

This VM is behind a proxy server and I can see traffic going through the proxy, however I am not able to login to the registry

[root@nrc3laquatest01vm etc]# docker login registery.aquasec.om
Username: test@testemail
Password:
Error response from daemon: Get https://registery.aquasec.com/v2: dial tcp: lookup registery.aquasec.om on 10.13.60.1:53: no such host

[root@nrc3laquatest01vm etc]# curl https://registery.aquasec.com --verbose

  • About to connect() to proxy 10.13.110.180 port 80 (#0)
  • Trying 10.13.110.180…
  • Connected to 10.13.110.180 (10.13.110.180) port 80 (#0)
  • Establish HTTP proxy tunnel to registery.aquasec.om:443

CONNECT registery.aquasec.om:443 HTTP/1.1
Host: registery.aquasec.om:443
User-Agent: curl/7.29.0
Proxy-Connection: Keep-Alive

< HTTP/1.1 503 Service Unavailable
< Mime-Version: 1.0
< Date: Wed, 22 Apr 2020 16:05:42 GMT
< Content-Type: text/html
< Connection: keep-alive
< Proxy-Connection: keep-alive
< Content-Length: 2324
<

  • Received HTTP code 503 from proxy after CONNECT
  • Connection #0 to host 10.13.110.180 left intact
    curl: (56) Received HTTP code 503 from proxy after CONNECT

Maybe this helps: https://stackoverflow.com/questions/46036152/lookup-registry-1-docker-io-no-such-host

1 Like

It worked, thank you very much