Selfhosted

63722 readers

798 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

Question about using gluetun for other containers (lemmy.world)

submitted 4 hours ago* (last edited 4 hours ago) by chagall@lemmy.world to c/selfhosted@lemmy.world

5 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

[–] sarahreid@lemmy.world 7 points 4 hours ago (1 children)

Yeah, depends_on only works inside a single compose file/project, so it can't see gluetun from stack 2 — that's why you're getting the undefined error. There's no built-in cross-stack depends_on, unfortunately.

The cleanest fix IMO is to merge them into one compose file if you can, then depends_on with service_healthy works for everything. If you really want to keep them seperate, a couple of options:

Start stack 1 first, then have a small wait script before stack 2, something like looping on docker inspect until gluetun's health status is healthy, then docker compose -f stack2.yml up -d. A bit clunky, but it works and it's explicit.
Or use a systemd unit or a wrapper script that runs the two up commands in order, with the wait in between.
What I wouldn't do is just add a fixed sleep — gluetun can take a while to bring the tunnel up, and a sleep that works today will bite you on a slow day.

One caveat too: service_healthy only means the container is healthy, not neccessarily that the VPN tunnel itself is fully up, so it's still worth checking the torrent client actually has the VPN IP before you trust it. FYI, you can test that from inside the client container with curl to an IP checker.

[–] IronKrill@lemmy.ca 2 points 3 hours 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.