DNS Configuration of Runners.Docker should also Apply to Associated Services
Description
Following the insruction on using Docker-in-Docker, my runner came up with an unexpected error message
Error response from daemon: Get https://registry.mycompany.com/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
We used a docker:latest
as image and docker:dind
for services. We discovered that the dns
setting in the section [runners.docker]
does not apply to the service as well. Logging in to docker:dind
revealed /etc/resolv.conf
still having the defaults set rather than our custom IPs.
Proposal
Please consider the possibility to introduce an 'inheritance' of that settings to the specific services such that the mentioned tutorial also works for internal DNS.
[Update]
@powerhamster proposes a solution in !892 (closed). Big Thx!