119

gluetun: VPN client in a thin Docker container for multiple VPN providers (github.com)

submitted 1 year ago by anzo@programming.dev to c/piracy@lemmy.dbzer0.com

19 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[-] DengueDucky@lemmy.ml 8 points 1 year ago

What's the use case?

[-] eratic@feddit.uk 7 points 1 year ago* (last edited 1 year ago)

I use gluetun to route traffic from some of my containers that need a VPN. qBittorrent, Jackett etc. Some containers dont have the option to configure a proxy so you'd have to setup a VPN client within a container which isn't ideal. With gluetun its easy to attach a container to it and it just works

[-] Artaca@lemdro.id 1 points 1 year ago

Neat. I never need a VPN for more than a few days at a time, but if I ever sub to one long term I'll keep this in mind.

[-] sylverstream@lemmy.nz 1 points 1 year ago

Good point about Jackett! I had only set up qbittorrent to use vpn.

[-] anarchrist@lemmy.dbzer0.com 1 points 1 year ago

Why isn't it ideal? I'm currently using this setup with containers routed through a gluetun container connected to a vpn via wireguard, and it seems to be working fine. I've verified using curl inside the relevant containers to query an IP checker and I've also used a torrent IP checker to confirm my torrent client isn't leaking my IP.

[-] conciselyverbose@kbin.social 5 points 1 year ago

I think he's saying that manually configuring all the containers (without this tool) isn't ideal.

[-] anarchrist@lemmy.dbzer0.com 2 points 1 year ago

Oh sure yeah it did suck 😁

[-] eratic@feddit.uk 3 points 1 year ago

Also the biggest benefit; You only need 1 VPN connection and 1 key pair for gluetun to connect everything. Most VPN providers limit the amount of active simultaneous connections. If you have lots of containers that need it then it's not possible