Our great sponsors
-
gluetun
VPN client in a thin Docker container for multiple VPN providers, written in Go, and using OpenVPN or Wireguard, DNS over TLS, with a few proxy servers built-in.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
Basically, I would like that few of my containers to use a proxy whenever they need to access the external world (e.g. Sonarr and its friends). At the moment, for Deluge I am using binhex docker image, an all in one solution for torrent, vpn and so on. Just to add an extra security layer, I would like to obfuscate from my ISP all the calls that the *Arr friends are doing to the usual search engines.
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 also have found this MullvadProxy which sounds more what I am looking for, but it looks a bit more complex and I don't fully get the role of all the components in the docker-compose example. Moreover it doesn't seem to be maintained anymore.