docker-openvpn VS gluetun

Else - https://github.com/kylemanna/docker-openvpn

When I look into vpn servers, I find easy installers, which directly work on linux (e.g. angristan/wireguard-install) or also vpns, which operate from docker (like kylemanna/docker-openvpn). Then there are options, where multiple things are included, like firezone or this. I am not so sure how well they integrate with my reverse proxy and some seem to be much more complicated than others.

This repo based on kylemanna/docker-openvpn but have Makefile with useful commands for comfortable OpenVPN setup.

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)?

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.

I use gluetun https://github.com/qdm12/gluetun supports multiple vpn providers

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

Have you ever heard about gluetun? I think it could be a good solution, or at least this is what I’m using and liking it so far to route my torrent client downloads

Gluetun - Creates the VPN connection

Not sure of a free one. I use NordVPN with this docker container https://github.com/qdm12/gluetun and it works great.

It's a bit complex but I use a setup of three docker containers which all share the same networking. I use Gluetun (https://github.com/qdm12/gluetun) as the VPN client and qbittorrent as the torrent client (I use the linuxserver io image but any should qbittorrent client should work). For the port forwarding I use https://github.com/soxfor/qbittorrent-natmap which uses nat-pmp to request a port from ProtonVPN via the Gluetun interface and then automatically updates it in qbittorrent. Gluetun apparently supports Proton port forwarding by default and exposes the port via its API if you want to write your own script, but I couldn't get it to work and it uses openvpn. This setup uses a wireguard config on gluetun from Proton with nat-pmp enabled. I run this on a random weak decade old computer 24/7 but in a desktop environment you should be able to just run it on Docker desktop when you want to torrent. The docker compose file in the natmap repo gives a good idea of this docker stack.

There is https://github.com/vishvananda/netlink which deals with low level networking stuff, maybe helping out there would be nice. I use it for https://github.com/qdm12/gluetun (also in Go)