New "AdGuard Home Handle Client Requests" feature has a bug

When “AdGuard Home Handle Client Requests” is enabled, it prevents docker from updating.

I get the following error when trying to update the docker containers:

Error response from daemon: Head “https://registry-1.docker.io/v2/containrrr/watchtower/manifests/latest”: Get “https://auth.docker.io/token?scope=repository%3Acontainrrr%2Fwatchtower%3Apull&service=registry.docker.io”: dial tcp: lookup auth.docker.io on 10.5.0.1:53: read udp 10.5.0.6:59815->10.5.0.1:53: i/o timeout

Disabling the new feature fixes docker updating. Could you guys test on your end? From the error it looks like udp is failing, but not sure. Maybe an extra firewall rule is required.

Hi John,

Enabling “AdGuard Home Handle Client Requests” will redirect all DNS queries to AdGuard port 3053. This means that if Docker queries DNS via a specific server, such as 10.5.0.1(like an internal network), it will also be redirected and then fail.

This behavior is expected. Do you have any advice haha?

1 Like