whenever I try to run a podman container, it’ll through:
Error: running container create option: container has joined pod 4f[long_string]b1f and dependency container 34[long_string]9cd is not a member of the pod: invalid argument
An example of a dependent container compose file looks like this:
services:
docs.linuxserver.io/images/docker-qbittorrent
qbittorrent: image: lscr.io/linuxserver/qbittorrent:latest container_name: qbittorrent environment: - WEBUI_PORT=8000 - PUID=0 - PGID=0 volumes: - ./config:/config:Z - ./files:/media restart: always depends_on: - gluetun network_mode: “container:gluetun”
MangoPenguin@lemmy.blahaj.zone 1 month ago
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.
swooosh@lemmy.world 1 month ago
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
Live2day@lemmy.sdf.org 1 month 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?
lemmyvore@feddit.nl 1 month ago
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.