23
Question about using gluetun for other containers (lemmy.world)
submitted 1 day ago by to c/selfhosted@lemmy.world
8 comments fedilink hide all child comments
 

I use gluetun, my arr stack and bittorrent client in a single docker-compose. I use the syntax

    depends_on:
      gluetun:
        condition: service_healthy

in the stack to make sure that the bittorrent client doesn't try to connect too early. All that works great.

I also use that same VPN connection for other containers too (not in the same docker-compose stack). I do that by simply using network_mode: "container:gluetun" in the second yaml file. But I'd like to use the same depends_on syntax. But it errors out because gluetun is undefined in the second stack.

So my question is, how do I make sure the containers in docker compose stack 2 start after docker compose stack 1 (the one with gluetun) is healthy?

you are viewing a single comment's thread
view the rest of the comments
[–] 2 points 1 day ago

One option nobody mentioned: Compose has a top-level include: (Compose v2.20+). In stack 2 add

include:
  - ../stack1/docker-compose.yml

and gluetun becomes part of the same project, so depends_on: gluetun: condition: service_healthy works again. The catch is that docker compose up/down in stack 2 now manages gluetun too, so it's best if stack 1 is only gluetun and everything else lives in its own files.

  • permalink
  • fedilink
  • source
    •