You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My image is image: mvance/unbound:latest.
Current healthcheck command is drill @127.0.0.1 cloudfare.com
I setup unbound in a subnet 172.19.0.x. This drill command fails when using 127.0.0.1, causing the healthcheck to only show unhealthy.
I think it is because it is expecting unbound to be run in the host network.
But in the /etc/resolv.conf the nameserver is 127.0.0.11, so, I tried drill @127.0.0.11 cloudfare.com and it works.
My image is
image: mvance/unbound:latest
.Current healthcheck command is
drill @127.0.0.1 cloudfare.com
I setup unbound in a subnet
172.19.0.x
. This drill command fails when using127.0.0.1
, causing the healthcheck to only showunhealthy
.I think it is because it is expecting unbound to be run in the host network.
But in the
/etc/resolv.conf
the nameserver is127.0.0.11
, so, I trieddrill @127.0.0.11 cloudfare.com
and it works.As far as I understand
127.0.0.11
is the default Docker nameserver (DNS).https://medium.com/@prajwal.chin/understanding-docker-dns-2ed4b070a0
Therefore, should the default healthcheck be changed to use
127.0.0.11
instead?Thanks,
Bruno
The text was updated successfully, but these errors were encountered: