docker-wireguard-pia VS gluetun

https://github.com/thrnz/docker-wireguard-pia works great for me

I'm in need of help & guidance here. I have a DS 1821+ running the latest DSM 7.1 packages. I've installed Docker and I'm running a few *arr's with no problem using using the information here (https://trash-guides.info/Hardlinks/How-to-setup-for/Synology/). I also have qBitTorrent working, but I'd like to have that traffic routed through a VPN. I installed this Docker image (https://github.com/thrnz/docker-wireguard-pia), but now I'm lost.

The stack (found here, and the extra variables here):

I have set up a new QNAP NAS and have a wireguard docker container that I've ported over to it. The container worked on a completely different system, but on the new QNAP NAS it won't work due to an issue with wg-quick and certain functions not being available on the QNAP kernal. The container in question uses the thrnz/docker-wireguard-pia image.

2) Also underrated because it's the only docker image for a VPN provider that supports portforwarding & automatically updates the configured port in QBittorrent settings: https://github.com/thrnz/docker-wireguard-pia

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