Open kfooze opened 2 years ago
Could consider using qdm12/gluetun.
Has many pre-set docker configuration files for popular VPNs.
To sum it up, the port you'd map for a container you want to run through a VPN would instead be mapped in gluetun.
The original container would instead use network_mode: "service:gluetun"
in its configuration block.
See here for connecting containers to gluetun, and check "Providers" list in the Table of Contents for examples of preset configurations.
Obviously this requires input from the user, but that's what the setup cli's for right?
Here's my Docker config as an example. Prowlarr and FlareSolverr are ran through Gluetun.
For Prowlarr to access Radarr and Sonarr, I created a Docker Network, added the two to it, gave them their own local subnet addresses, and specified the outbound subnet in Gluetun. Prowlarr resolves their subnet IPs instead of localhost.
Note that this method is just a workaround. The contributors at Gluetun are working a nicer method.
docker network create --subnet=172.18.0.0/16 gluetun_outreach
There are nicer methods out there, but it's a point of reference and it works for me. Hope it helps!
Came across this, might be useful: https://github.com/DyonR/docker-qbittorrentvpn
Hi @kfooze, were you able to do this? I would like to be able to use this stack with nordvpn and don't really know my way around docker. Any help would be appreciated. Thanks!
As a user of an ezarr stack, id like to be able to utilize a vpn to encrypt only the torrent client traffic, so i have privacy and my ip provider will not be aware of the traffic
I'd like one of two options, a new vpn client service with the traffic from the torrent client routed through it or the torrent client service to include the openvpn client that can be configured appropriately.