dockerMullvadVPN VS gluetun

I used this guide to make a docker compose with qbittorrent bound through openvpn. I've had no issues with speed.

This is something that was worrying me a bit. I thought about running a sidecar but not sure. I found this and this and was hoping one of them would work, but I'll see this once I get to it.

Hi there, I'm setting up a docker config to use mullvad via openvpn following this tutorial

Or a more manual approach with more options: https://github.com/nickkjolsing/dockerMullvadVPN/blob/master/README.md

I set up a Mullvad docker container and a transmission docker container, routed through the Mullvad. I tested a 5 GB download, expecting router would see the traffic as TLS. It saw it as DNS. It sees nothing it considers torrent traffic.

After several hours of tinkering I managed to finally have a docker container running in container station that has access to the internet and is finally using my mullvad-openvpn configuration files. I've used this tutorial, which is not QNAP specific https://github.com/nickkjolsing/dockerMullvadVPN/blob/master/README.md I followed the steps and created a compose file, using the +Application function in Container Station GUI The Container starts up and connects to the vpn server flawlessly. I know that, because in the console I can see the OpenVPN message: "Initialization Sequence Completed" However, before I can /bin/sh into the container to confirm if the container is really connecting to the internet through VPN tunnel, the container keeps resetting itself. It just stops for a few seconds, and then starts up again, establishing connection to the vpn service provider (mullvad). I already tried different options in the compose file in line restart: unless-stopped (I tried: always and never) But it does not changes the behaviour. I know I do not have much memory (TS251+, 2GB RAM) But one openvpn container should be managable

Here's the instructions that I followed: https://github.com/nickkjolsing/dockerMullvadVPN

healthcheck: # https://github.com/qdm12/gluetun/issues/641#issuecomment-933856220 test: "curl -sf https://example.com || exit 1" interval: 1m timeout: 10s retries: 2

I have containers a,b,c. Container C is running Gluetun (https://github.com/qdm12/gluetun) which is a VPN container.

The last couple of years I have been donating to Gluetun.

One option I could find is Gluetun, which looks very popular and actively maintained. In this case we have one single point of contact with VPN provider. The other containers should be run with network_mode: service:gluetun. If I understand correctly, those container will use VPN for every network operation, even for inter-container communication. Would they be visible for the containers not attached to gluetun (e.g. the SWAG reverse proxy)?

Try setting it up. https://github.com/qdm12/gluetun See if it works for your needs.

After some digging around, I found this project, which I think should get a lot more light on itself. It allows to setup port-forwarding on linux very easily, together with a lot of other things !

I setup Gluetun with qbittorrent in docker. Gluetun connects to the nord via manual login and I get to choose the specific servers I want it to you in its environment variables.

Hi guys, I have a dumb question: according to their github page, one of the features is the killswitch. It is not clear to me whether this would shutdown other containers (connected to it) when vpn drops, or only when the whole internet connection goes down

# See https://github.com/qdm12/gluetun/wiki