I have tailscale set up on my main server, and a couple of Android devices. Almost everything is working nicely.
The only issue I have right now is that when tailscale is up, registry-1.docker.io does not always resolve when I use docker-compose. Sometimes it does, and sometimes it does not. Occasionally, I will see a different docker.io subdomain not resolve either. If I do a tailscale down, and then do the same commands, I do not have the issue. This leads me to think that something with tailscale and the way I have it set up is causing the problem. Also, I have not seen any issues with any other hosts. Just docker.io.
Here is what I see when I do a docker-compose pull. Note that the first time, everything was fine. I ran it again, immediately after the first run, and the docker.io was resolved for some calls, but not for others.
@nuc > /opt/Docker/Servers > docker-compose pull
Pulling Heimdall ... done
Pulling snippet-box ... done
Pulling uptime-kuma ... done
Pulling Unifi ... done
Pulling diun ... done
Pulling mealie ... done
Pulling FirefoxSyncserver ... done
Then I immediately run the same command, with different results
@nuc > /opt/Docker/Servers > docker-compose pull
Pulling Heimdall ... error
Pulling snippet-box ... done
Pulling uptime-kuma ... error
Pulling Unifi ... error
Pulling diun ... error
Pulling mealie ... done
Pulling FirefoxSyncserver ... error
ERROR: for Heimdall Head "registry-1.docker.io/v2/linuxserver/heimdall/manifests/latest": dial tcp: lookup registry-1.docker.io: no such host
ERROR: for uptime-kuma Head "registry-1.docker.io/v2/louislam/uptime-kuma/manifests/1": dial tcp: lookup registry-1.docker.io: no such host
ERROR: for Unifi Head "registry-1.docker.io/v2/linuxserver/unifi-controller/manifests/latest": dial tcp: lookup registry-1.docker.io: no such host
ERROR: for diun Get "registry-1.docker.io/v2/": dial tcp: lookup registry-1.docker.io: no such host
ERROR: for FirefoxSyncserver Get "registry-1.docker.io/v2/": dial tcp: lookup registry-1.docker.io: no such host
ERROR: Head "registry-1.docker.io/v2/linuxserver/heimdall/manifests/latest": dial tcp: lookup registry-1.docker.io: no such host
Head "registry-1.docker.io/v2/louislam/uptime-kuma/manifests/1": dial tcp: lookup registry-1.docker.io: no such host
Head "registry-1.docker.io/v2/linuxserver/unifi-controller/manifests/latest": dial tcp: lookup registry-1.docker.io: no such host
Get "registry-1.docker.io/v2/": dial tcp: lookup registry-1.docker.io: no such host
Get "registry-1.docker.io/v2/": dial tcp: lookup registry-1.docker.io: no such host
Here is my resolv.conf when tailscale is running:
# resolv.conf(5) file generated by tailscale
# DO NOT EDIT THIS FILE BY HAND -- CHANGES WILL BE OVERWRITTEN
nameserver 100.100.100.100
search xxxx.xxxxxx.com.beta.tailscale.net
My tailscale settings on the server are:
- subnet 192.168.1.0/24 so I can access other servers and services without running tailscale on everything
- server is set as an exit node
- MagicDNS is enabled
- Global Nameservers has two entries (192.168.1.XXX) so I can resolve my local services
- Override local DNS is active
- Everything else is default
I have used nslookup multiple times, and the hostname always resolves
@nuc > /opt/Docker/Servers > nslookup registry-1.docker.io
Server: 100.100.100.100
Address: 100.100.100.100#53
Non-authoritative answer:
Name: registry-1.docker.io
Address: 3.215.51.67
Name: registry-1.docker.io
Address: 54.242.59.189
Name: registry-1.docker.io
Address: 54.83.42.45
It seems to be DNS related, but I can’t seem to figure out where the issue is.
Any ideas of what the issue could be?
Thanks
ps. If there is any additional info that would be useful, please let me know, and I will provide it