• roofuskit@kbin.social
      link
      fedilink
      arrow-up
      19
      ·
      1 year ago

      The container connects to the VPN and only the VPN, now you can route whatever docker containers you want through that container as a network. Now that one VPN connection can serve any container you want.

    • eratic@feddit.uk
      link
      fedilink
      English
      arrow-up
      6
      ·
      edit-2
      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

      • anarchrist@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        1
        ·
        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.

            • eratic@feddit.uk
              link
              fedilink
              English
              arrow-up
              2
              ·
              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

      • Artaca@lemdro.id
        link
        fedilink
        English
        arrow-up
        1
        ·
        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.