Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ping within the gluetun network stack #19

Closed
shuntera opened this issue Oct 8, 2023 · 2 comments
Closed

ping within the gluetun network stack #19

shuntera opened this issue Oct 8, 2023 · 2 comments

Comments

@shuntera
Copy link

shuntera commented Oct 8, 2023

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'"

@JermellB
Copy link

JermellB commented Oct 14, 2023

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.

@qdm12
Copy link
Owner

qdm12 commented Nov 8, 2023

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

@qdm12 qdm12 closed this as not planned Won't fix, can't repro, duplicate, stale Nov 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants