• somebodyknows@lemmy.world
    link
    fedilink
    English
    arrow-up
    8
    ·
    1 year ago

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

    • Solar Bear@slrpnk.net
      link
      fedilink
      English
      arrow-up
      11
      ·
      edit-2
      1 year ago

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

      • dan@upvote.au
        link
        fedilink
        English
        arrow-up
        3
        ·
        1 year ago

        But you can just do that with a regular Wireguard container. Does this one do anything special? I haven’t looked into it yet but I guess it’s pre-configured for some providers?

    • gobbling871@lemmy.world
      link
      fedilink
      English
      arrow-up
      6
      ·
      edit-2
      1 year 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.world
        link
        fedilink
        English
        arrow-up
        6
        ·
        1 year 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