docker-openvpn VS gluetun

J'ai trouvé pour openvpn ces deux: [https://hub.docker.com/r/kylemanna/openvpn [https://hub.docker.com/r/linuxserver/openvpn-as DMAM

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

I'm fighting a weird issue plaguing both a friend and myself. I'm using the kylemanna/openvpn docker container on the server side and whatever OpenVPN client there is on clients.

I'm using the latest kylemanna/openvpn container for the server, running on Debian 11 x86_64.

Talking with some contacts I have, right now the big ask is for secure VPNs. If you can host a server (location should be outside the US and other western countries so CSPs may by your best option) that would perhaps be the best. OpenVPN is a solid choice and there are docker images you can use to readily deploy: https://github.com/kylemanna/docker-openvpn a solution.

3 . Clone the project from this repo (https://github.com/kylemanna/docker-openvpn) with this command

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.

I know that tunneler supports OpenVPN, so I imagine I could use kylemanna/openvpn but I can't figure out how to set it up...

I'm trying to setup an openvpn docker container in a one to many setup. I know there exist already solutions but I'm kind of scared that it hasn't been updated in a year (OpenVPN Docker Container).

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