Comment on dependent containers don't work anymore because of network_mode
swooosh@lemmy.world 4 months agoI’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
You’re attempting to run the qb container in the gluetun network stack. You need to give it time to start. When they’re in the same compose file they can be ordered properly but when they’re different files it doesn’t care.
Check out the full options (long form) to depends: and see if you can add a delay and a health check.
It has worked for months. Thank you. I’ll se what I can do.
Live2day@lemmy.sdf.org 4 months ago
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?
ElderWendigo@sh.itjust.works 4 months ago
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.
swooosh@lemmy.world 4 months ago
Immich has multiple services running. Having that within one file is good in my opinion. Or nextcloud with an external database.