Not great.Īfter two days of trying stuff out and searching the internet, I found the working solution on a blog post from 2021 which sadly already no longer exists. The only issue was that while the BitTorrent client was perfectly shielded by the VPN, I could no longer access the client myself.

With some experimenting, I got it working 90%. Our solution will be to add another container which connects to the VPN and route our sensitive container through the VPN container. One could install the Wireguard client straight on the machine and route both containers through the VPN, but for various reasons, that's now what we want here. Our situation is this: our homeserver (could be a Linux machine, a Raspberry Pi…) runs two docker containers, one which is fine to be directly connected to the internet and one which would benefit from VPN access. Oh yes, it's Wireguard time.Īs VPN provider, I use Mullvad. I already had a similar solution using OpenVPN but it was time for an upgrade. If like me you have your BitTorrent client installed as a container on a homeserver to make sure it's always connected but you don't want to route your other containers through a VPN, you'll probably want to use a VPN-in-a-container and route your BitTorrent client through it. After all, you wouldn't want your ISP knowing which Linux distribution you download and share. Some containers just aren't meant to be connected directly to the internet.

#vpn #docker #wireguard Your container might benefit from VPN access Contact Wireguard and docker: providing VPN access to arbitrary containers

Mullvad wireguard linux