search

qdm12 / gluetun

VPN client in a thin Docker container for multiple VPN providers, written in Go, and using OpenVPN or Wireguard, DNS over TLS, with a few proxy servers built-in.
https://hub.docker.com/r/qmcgaw/gluetun
MIT License
6.89k stars 335 forks source link

Wiki issue: inter containers networking and firewall rules #1379

Open avt00 opened 1 year ago

avt00 commented 1 year ago

URL to the Wiki page

https://github.com/qdm12/gluetun/wiki/Inter-containers-networking

What's the issue?

Please add a note regarding the FIREWALL_OUTBOUND_SUBNETS parameter to the wiki page. Currently, it's missing, and this can lead to connectivity issues between two containers. For example, 172.22.0.22/16 is unreachable from a gluetun container if FIREWALL_OUTBOUND_SUBNETS is not set in the gluetun container's environment options.

itsokk commented 1 year ago

Thank you so much for opening an issue about this, I just spent 30 minutes trying to fix. I hope somebody will put it in the wiki soon.

qdm12 commented 1 year ago

Sorry for the delay; this is the case if Gluetun isn't in the same docker network as the other containers right?

It's mentioned in the wiki page must be in the same Docker network 🤔

avt00 commented 1 year ago

My containers are on the same network. Just in case, here's how it works for me:

gluetun and qbittorrent are on the same network called gluetun_network. jackett is not on the same network as gluetun. In jackett's container settings, the network_mode is "container:gluetun".

In order for jackett and qbittorrent to communicate with each other, I had to use FIREWALL_OUTBOUND_SUBNETS to make it work.