view the rest of the comments
Selfhosted
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:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
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!
Generally to depend on a container it needs to be in the same compose project, so if you move gluetun into the one with qbittorrent it should work fine.
I've been running that since many months like that. Why did that break now ...
It works in the same file. I don't want to have 10 containers in the same compose file.
I checked, it works in the same file, thx.
Removing "depends: gluetun" does not work either
But that's like the whole point of docker compose. If you are just going to have 1 container per file what benefit are you even getting out of using a compose file?
Docker compose is just a setting file for a container. It's the same advantage you get using an ssh config file instead of typing out and specifying a user, IP, port, and private key to use each time. What's the advantage to putting all my containers into one compose file? It's not like I'm running docker commands from the terminal manually to start and stop them unless something goes wrong, I let systemd handle that. And I'd much rather the systemd be able to individually start, stop, and monitor individual containers rather than have to bring them all down if one fails.
Immich has multiple services running. Having that within one file is good in my opinion. Or nextcloud with an external database.