24
Question about using gluetun for other containers (lemmy.world)
submitted 2 days 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 2 days ago

Darn. I had the same question as OP but have been working around it by combining everything into the same stack. It's just a bit of a pain to edit the stack every time I want to test something or retire a service.

Good work-arounds though! Maybe I should move to a script-based startup... Only trouble is all my containers are tagged with restart: unless-stopped so Docker restarts all of it at once on reboot which would mess up the order. Hmm.

  • permalink
  • fedilink
  • source
  • parent