GitHub - qdm12/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.
github.com
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. - GitHub - qdm12/gluetun: VPN clien...
  • somebodyknows@lemmy.worldEnglish
    6·
    2 years ago

    Couldn’t understand if it’s a client in the sense other docker containers can use it, or what. Could somebody please clarify?

    • gobbling871@lemmy.worldEnglish
      4·
      2 years ago

      It’s a vpn client on steroids that creates a VPN network (based on your provider) which you can then use to run docker containers inside of, as well as create http & shadowsocks proxies for your VPN network etc.

      • finestnothing@lemmy.worldEnglish
        4·
        2 years ago

        To build on this since I have this setup now, it basically creates a new docker network that you can attach containers to, and have all of their traffic routed through it. Basically I have the gluetun container running, then in my qbittorrent docked-compose I have network_mode: "container:gluetun".

        One thing to watch out for is you have to specify the ports in the gluetun docked-compose instead of in each docked-compose.

        Additionally, if gluetun shuts down and the apps using it don’t, you’ll have to restart the apps using it. Not an issue if it’s all in the same docker-compose file, but I like separating docker-compose services so I have qbittorrent/docker-compose.yml and gluetun/docker-compose.yml

    • Solar Bear@slrpnk.netEnglish
      1·
      2 years ago

      It’s a docker container that runs an OpenVPN/Wireguard client in order to provide a connection for other containers, yes.

  • macgregor@lemmy.worldEnglish
    4·
    2 years ago

    Switched to qbittorrent+gluetun side car recently and it’s been pretty good compared to the poorly maintained combo torrent+OpenVPN images I was using. Being able to update my torrent client image/config independent from the VPN client is great. Unfortunately most of the docs are Docker focused so it’s a bit of trial and error to get it setup in a non-docker environment like Kubernetes. Here’s my deployment in case it’s useful for anyone. Be careful that you configure qbittirrent to use “tun0” as it’s network interface or you will be exposed (got pinged by AT&T before I realized that one). I’m sure there’s a more robust way to makeuse of gluetun’s DNS over TLS and iptables kill switch that doesn’t require messing with qbittorrent config to secure, but that’s what I have so far and it works well enough for now.

  • JTode@lemmy.worldEnglish
    2·
    2 years ago

    Have been using this for a good six months, works a charm. Not that I steal movies or anything, but I’ve received no bitchy letters from my ISP.

    edit, protip: I got very confused for like 30 hours about how I connect other containers to this, and what you do is, the gluetun container the network stack for the container you want to VPN.

    • NaturallyAsh@szmer.infoEnglish
      1·
      1 year ago

      I went from Mullvad to AirVpn a month ago. I really like it so far. The web ui takes some getting used to. But I haven’t had any issues and port forwarding works very well.