Comment on Separate Docker stacks using gluetun networking

CumBroth@discuss.tchncs.de ⁨3⁩ ⁨weeks⁩ ago

• lem@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

  I have gluetun and qbittorrent running separately and this works for me.

  source
• Dust0741@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

  network_mode is only for multiple containers in the same stack.

  source

  • CumBroth@discuss.tchncs.de ⁨3⁩ ⁨weeks⁩ ago

    Uhh, I think you might be confused. Let me explain a bit more:

    1. Services and Containers aren’t the same thing. The distinction usually doesn’t matter in typical self-hosting scenarios, but in this case it does.

    In short: Services are what you define in a compose file; Containers are what you spin up based on those service definitions.

    2. network_mode is a service attribute and it can be defined for each service separately.
    3. network_mode: “service:{name}” requires the service being referenced to be part of the same stack. This is probably what you were thinking of when you wrote this reply.
    4. network_mode: “container:{name}” can freely reference any preexisting container. This helps you achieve what you want. You can define your gluetuncontainer independently, along with any services you might want to be part of the same stack, and give it a unique identifier usingcontainer_name: myIndependentGluetun. After spinning it up, run your Qbittorrentcontainer or whatever service you want to route through thegluetuncontainer after addingnetwork_mode: “container:myIndependentGluetun”.

    source

    • Dust0741@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

      Oooooooooooo I totally was confused. Thank you for this!!!

      source
    • Dust0741@lemmy.world ⁨2⁩ ⁨weeks⁩ ago

      Amazing this worked great!!!

      One question though; How do I get qbittorrent to auto reconnect if gluetun gets restarted? (currently checking public ip per above fails if gluetun gets restarted, and the only way to fix is by restarting qbittorrent.)

      source

      • CumBroth@discuss.tchncs.de ⁨2⁩ ⁨weeks⁩ ago

        This is an annoying quirk in the way docker handles networking between containers and I couldn’t find a good solution for this issue when I was trying out network_mode. I just couldn’t find a way to set docker up to automatically restart the dependent container. You can achieve this with services defined in the same stack (using depends_on), but I don’t know if it’s possible with your current setup.

        That’s why I mentioned manual routing in my other reply. It’s annoying to set up, but more convenient because you avoid having to manage restarts (or figuring out how to get docker to do it, which may not be possible in this case).

        source