Pretty sure I’m also seeing similar issues too, but just straight up using the
plugins/docker plugin to build Docker images. I added some extra logging to a custom version of the plugin and I see errors like this (which currently are obscured from the user):
Error authenticating to Docker daemon (retrying 538/600): exit status 1
WARNING! Using --password via the CLI is insecure. Use --password-stdin.
Error response from daemon: Get https://r.mills.io/v2/: dial tcp: lookup r.mills.io on 127.0.0.11:53: read udp 127.0.0.1:60798->127.0.0.11:53: read: connection refused
I know it’s not a networking problem, because I also put some extra long retries in the custom version of
plugins/docker so I can
docker exec into the spaned runner container to see wtf is going on. Here’s what I find:
- Networking works fine, local LAN as well as Internet. i.e:
ping <ip> responds just fine.
- DNS fails with the above.
Once I edit
/etc/resolv.conf in the container and swap
nameserver 127.0.0.11 with my local DNS server on the LAN (e.g:
10.0.0.1) DNS works (obviously).
It seems the builtin DNS server in the Docker daemon is not responding for some reason and I’ve been debugging this for weeks with no succeed. I haven’t been able to find any good hints as why either as this is a really hard topic to web search.
@bradrydzewski You got any ideas?