I would like to run Gluetun in its own compose.yaml file, and run qbittorrent in its own compose.yaml file. I want to use the vpn connection Gluetun makes for qbittorrent.

Does anyone have examples of this working? I’ve been messing with the containers, and different docker networks can I cannot get it working.

(my test has been running docker exec -it qbittorrent curl -s https://ifconfig.me/)

  • Guillaume Rossolini@infosec.exchange
    1·
    8 days ago

    @Dust0741 you could also get each container to access the other by specifying the stack prefix

    Say you have stack1 and stack2

    Stack1 can have

    networks:  stack2_default:    external: trueservices:  foo:    networks:      - default      - stack2_default
  • ki9@lemmy.gf4.pwEnglish
    1·
    8 days ago

    In the qbt compose file, you can set

    network_mode: container:gluetun

    To use Gluetun’s network namespace for your qbt container. This is how I use qbt over vpn.

      • CumBroth@discuss.tchncs.deEnglish
        6·
        8 days 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.

        1. network_mode is a service attribute and it can be defined for each service separately.
        2. 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.
        3. network_mode: "container:{name}" can freely reference any preexisting container. This helps you achieve what you want. You can define your gluetun container independently, along with any services you might want to be part of the same stack, and give it a unique identifier using container_name: myIndependentGluetun. After spinning it up, run your Qbittorrent container or whatever service you want to route through the gluetun container after adding network_mode: "container:myIndependentGluetun".

        You could also route it manually. That’s a more advanced solution, but it’s more convenient than the network_mode approach. More on this here: https://discuss.tchncs.de/post/19039498