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
Funny enough; this is why I integrated traefik into my stack.
Realized that I couldn't do this.
Most likely a me problem though, I'm not a networking guy.
It's because by default DNS over TLS is used to do DNS resolution through the tunnel and then encrypted until i.e. Cloudflare DNS servers.
Anyway, you should NOT use the Docker network DNS in Gluetun, since that would mean all DNS traffic would go through it and not through the tunnel at all. I'm working slowly on a solution please subscribe to qdm12/gluetun#281
Finally, you can still ping using the sonarr Docker network ip address, for example docker exec -it gluetun ping 10.0.0.17
Should i be able to ping around the various containers under the network stack for all the service/containers in the same docker compose file.
eg if I have the sonarr service running under gluetun in the same docker-compose file should I be able to perform:
docker exec -it gluetun ping sonarr
and get a result?
all I get right now is "ping: bad address 'sonarr'"
The text was updated successfully, but these errors were encountered: