Sometimes (roughly every 20 builds) I get this error:
Error response from daemon: Get https://index.docker.io/v1/users/: dial tcp 52.207.178.113:443: connect: network is unreachable
Is this a known issue? How can I debug if this is an issue on the Circle side or with index.docker.io itself?
I have never experienced this locally.
This might be related: https://forums.docker.com/t/docker-login-dial-tcp-lookup-index-docker-io-read-udp-i-o-timeout/14844/11
I see the same issue in our build from time to time.
I’m getting this continuously at the moment.
+ docker login --username xxxx --password xxxx
Email: Error response from daemon: Server Error: Post https://index.docker.io/v1/users/: dial tcp: lookup index.docker.io on 172.17.8.1:53: no such host
But I put a “dig” for the host into the deploy script and that works fine…
+ dig index.docker.io
; <<>> DiG 9.9.5-3ubuntu0.7-Ubuntu <<>> index.docker.io
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 51301
;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;index.docker.io. IN A
;; ANSWER SECTION:
index.docker.io. 60 IN CNAME elb-io.us-east-1.aws.dckr.io.
elb-io.us-east-1.aws.dckr.io. 60 IN CNAME us-east-1-elbio-rm5bon1qaeo4-623296237.us-east-1.elb.amazonaws.com.
us-east-1-elbio-rm5bon1qaeo4-623296237.us-east-1.elb.amazonaws.com. 60 IN A 34.234.103.99
us-east-1-elbio-rm5bon1qaeo4-623296237.us-east-1.elb.amazonaws.com. 60 IN A 52.87.47.61
us-east-1-elbio-rm5bon1qaeo4-623296237.us-east-1.elb.amazonaws.com. 60 IN A 54.236.81.192
;; Query time: 52 msec
;; SERVER: 172.17.8.1#53(172.17.8.1)
;; WHEN: Mon Nov 20 14:12:31 UTC 2017
;; MSG SIZE rcvd: 212