Submitted 3 weeks ago by Dust0741@lemmy.world to selfhosted@lemmy.world
I would like to run Gluetun in its own compose.yaml file, and run qbittorrent in its own compose.yaml file. I want to use the vpn connection Gluetun makes for qbittorrent.
Does anyone have examples of this working? I’ve been messing with the containers, and different docker networks can I cannot get it working.
(my test has been running docker exec -it qbittorrent curl -s https://ifconfig.me/)
Maybe try this: docs.docker.com/compose/how-tos/…/merge/
I don’t want to merge them, I specifically would like them separate.
I had a problem similar to this and did not like the containers being binded to gluetun (problematic on docker daemon restarts, gluetun container being recreated, etc)
My solution was changing the gateway of each container to be routed through the tun. So first by having them both on the same internal network, then changing the entrypoint of the container I want tunneled to include the gateway change.
For example my entrypoint would be:
… && route del default && route add default gateway $GATEWAY_IP eth0
The container may be missing packages related to route so it may be necessary to modify the Dockerfile to install extra packages.
The reason the gateway must be set at the entrypoint is because docker overrides the gateway to correspond with the networking defined during container creation. And the entrypoint is the last thing executed before the container starts for realsies.
However gluetun also needs to work as a gateway which is done by modifying it’s iptables post-up rules file (at /iptables/post-rules.txt). I appended at the beginning of the file the following rules:
iptables -A FORWARD -i eth0 -o tun0 -s 172.84.0.0/24 -d 0.0.0.0/0 -j ACCEPT iptables -A FORWARD -i eth0 -o tun0 -m state --state RELATED,ESTABLISHED -j ACCEPT iptables -A FORWARD -i tun0 -o eth0 -m state --state RELATED,ESTABLISHED -j ACCEPT
What this does is accept any traffic from the net I have my gluetun and other container in, then forwards outgoing traffic to eth0 from tun0, and vice versa for incoming.
Sorry for wall of text this is not very straight forward :(
In the qbt compose file, you can set
network_mode: container:gluetun
To use Gluetun’s network namespace for your qbt container. This is how I use qbt over vpn.
I’m pretty sure this is the video I used to setup mine awhile back. I have my deluge docker networked into Gluetun. Everything else flows normal.
CumBroth@discuss.tchncs.de 3 weeks ago
You could use
network_mode: “container:<name>”instead ofservice:<name>. See here docs.docker.com/reference/compose-file/services/#…lem@lemmy.world 3 weeks ago
I have gluetun and qbittorrent running separately and this works for me.
Dust0741@lemmy.world 3 weeks ago
network_modeis only for multiple containers in the same stack.CumBroth@discuss.tchncs.de 2 weeks ago
Uhh, I think you might be confused. Let me explain a bit more:
ServicesandContainersaren’t the same thing. The distinction usually doesn’t matter in typical self-hosting scenarios, but in this case it does.In short:
Servicesare what you define in acomposefile;Containersare what you spin up based on those service definitions.network_modeis a service attribute and it can be defined for each service separately.network_mode: “service:{name}”requires the service being referenced to be part of the same stack. This is probably what you were thinking of when you wrote this reply.network_mode: “container:{name}” can freely reference any preexisting container. This helps you achieve what you want. You can define yourgluetuncontainer independently, along with any services you might want to be part of the same stack, and give it a unique identifier usingcontainer_name: myIndependentGluetun. After spinning it up, run yourQbittorrentcontainer or whatever service you want to route through thegluetuncontainer after addingnetwork_mode: “container:myIndependentGluetun”.