Debian running podman. Containers and compose files are managed with Dockge. qBit and Gluetun are on a single compose file and all qBit traffic is routed through Gluetun.
qBit seems to starts first before Gluetun is fully set up and qBit doesn’t see the open port. Every time I start them together, I have to manually restart qBit again once Gluetun is ready. Once it’s restarted, it shows as open and connected again.
I tried looking for ways to delay startup in a compose file but I didn’t get any results.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !piracy@lemmy.dbzer0.com
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
Did you specify a dependency? https://docs.docker.com/compose/compose-file/05-services/#depends_on
If qbit depends on gluetun it doesn’t start before it.
For this kind of question it’s always good to show the compose file(s)
I added a pastebin of the compose file
I tried adding depends_on to the qBit, but I got the same result. I think it’s already dependent on gluetun for the network_mode
Make a wait for the container.
https://docs.docker.com/compose/startup-order/
I added this to my qBit section:
It caused an error with gluetun somehow
You only need depends_on: gluetun. Did you observe the logs at boot? Do they still show that qbit starts first?
qBit starts second but Gluetun isn’t finished and doesn’t open the port for another few seconds, causing this problem