openvpn-client VS docker-wireguard

I use dperson/openvpn-client, which seems to do the trick for the most part. Ive got several packages that route through it using network_mode: "service:openvpn".

Gluetun has an integrated killswitch: https://github.com/qdm12/gluetun

I used to use https://github.com/dperson/openvpn-client which has a killswitch as well.

By kill-switch I mean iptables rules that don't let anything out if there's no VPN interface up. So you don't run the risk of leaking torrent stuff through your plain-text connection.

One of my Pi servers running a series of Docker services was taken out a few months back because an apt upgrade changed the compilation target of time_t causing me to have to spend a week untangling a web of dependencies to revert to an older version of musl.

I just tested the https://github.com/dperson/openvpn-client to use my NordVPN account and could get it working, the container connects succesfully! Can I somehow share this connection to other LAN devices (eg my TV) where I cant't install a VPN client?

I have gone down a rabbit hole today trying to route all Docker container traffic through OpenVPN. Previously I have used dperson/openvpn-client, but I would prefer to run OpenVPN directly on the host. With the VPN up on the host, the Docker containers make use of the VPN connection but if it drops they continue without it. Ideally there would be a kill switch to prevent this from happening.

I am looking to use my protonvpn subscription to use with an OpenVPN container (this one), but the documentation on both Protonvpn and the repo is pretty light on how to use it.

Hey there, I successfully managed to run this OpenVPN docker Container on my DS218+. I then connected another container to use this OpenVPN container as a network. Everything works like a charm.

OpenVPN client to route my illicit content through Pakistan (CyberGhost paid VPN)

As someone who's currently using dperson/openvpn-client with a Cyberghost VPN, what are the advantages of this container?

I'd like to integrate an application on a container that's connected to an OpenVPN server. I've found a convenient client base image to build on top of, but I can't seem to find the right way to do this.

https://github.com/linuxserver/docker-wireguard/issues/139

It’s probably better to just use the wireguard docker container setup instructions now: https://github.com/linuxserver/docker-wireguard?tab=readme-o...

I'm running linuxserver/docker-wireguard in Docker via docker-compose. It works great and I can access anything on my LAN via IP or DNS from my phone.

I'm trying to set up a Wireguard VPN server on an 2020 M1 Mac Mini running Fedora Asahi server through Docker.

You can add one to the docker compose file and then route other containers (especially qbittorrent) through it by setting network-mode. Read about it here: https://github.com/linuxserver/docker-wireguard

I checked /etc/sysctl.conf on the pi itself, and all lines are commented. Same on the docker container when I exec -it into it. https://github.com/linuxserver/docker-wireguard is the container I use

FWIW there is https://github.com/linuxserver/docker-wireguard/tree/alpine, which does just that really. It's a little more complicated because it still supports all the peer config envs, etc. but it's much smaller than the normal image because it doesn't have support for compiling and enabling the kernel module.

- I am using the linuxserver wireguard docker container: https://github.com/linuxserver/docker-wireguard