Pulp containers error during podman compose start up #760
Description
Version
pulp-oci-images:latest
Describe the bug
Running podman-compose up fails to start pulp containers when running it as described in the docs.
While the redis and postgres containers seem to start up fine, pulp_worker, signing_key_service and pulp_api output show errors while podman-compose up runs
[redis] | 1:M 13 Oct 2025 18:55:50.870 * Ready to accept connections tcp
[postgres] | 2025-10-13 18:55:50.922 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
[postgres] | 2025-10-13 18:55:50.950 UTC [28] LOG: database system was shut down at 2025-10-13 18:48:51 UTC
[postgres] | 2025-10-13 18:55:50.964 UTC [1] LOG: database system is ready to accept connections
[pulp_content] | Waiting on postgresql to start...
[pulp_content] | Postgres started.
[set_init_password_service] | Waiting on postgresql to start...
[set_init_password_service] | Postgres started.
[pulp_content] | Checking for database migrations
[set_init_password_service] | Checking for database migrations
[pulp_content] | Database migrated!
[pulp_content] | /usr/local/bin/pulpcore-content
[set_init_password_service] | Database migrated!
[migration_service] | Operations to perform:
[migration_service] | Apply all migrations: ansible, auth, certguard, container, contenttypes, core, deb, file, maven, npm, ostree, python, rpm, sessions
[migration_service] | Running migrations:
[migration_service] | No migrations to apply.
[pulp_worker] | Error: unable to start container 9fbe766f7a80288d3828287949e82638fb8bfc25c9d3da494ea583475d364ffd: generating dependency graph for container 9fbe766f7a80288d3828287949e82638fb8bfc25c9d3da494ea583475d364ffd: container 57d591971622a5c2d45739eeb776f619897cbd20ea148f4cc176d449bc1721c7 depends on container b9e6db903b62545ab723ac3e8146cf56f396543eea99507483a6035161ccedb5 not found in input list: no such container
[signing_key_service] | Error: unable to start container a0bf4fd5a3a0b0aba4643a7346dd24abb597a5a4ec43f4ca7b312808eccedc0d: generating dependency graph for container a0bf4fd5a3a0b0aba4643a7346dd24abb597a5a4ec43f4ca7b312808eccedc0d: container 57d591971622a5c2d45739eeb776f619897cbd20ea148f4cc176d449bc1721c7 depends on container b9e6db903b62545ab723ac3e8146cf56f396543eea99507483a6035161ccedb5 not found in input list: no such container
[pulp_api] | Error: unable to start container 584f8044eec95b0c5874168cecb268bbaa081a7efd6ac223268a109b54c57ec5: generating dependency graph for container 584f8044eec95b0c5874168cecb268bbaa081a7efd6ac223268a109b54c57ec5: container 57d591971622a5c2d45739eeb776f619897cbd20ea148f4cc176d449bc1721c7 depends on container b9e6db903b62545ab723ac3e8146cf56f396543eea99507483a6035161ccedb5 not found in input list: no such container
[pulp_content] | [2025-10-13 18:55:58 +0000] [1] [INFO] Starting gunicorn 23.0.0
[pulp_content] | [2025-10-13 18:55:58 +0000] [1] [INFO] Listening at: http://[::]:24816 (1)
[pulp_content] | [2025-10-13 18:55:58 +0000] [1] [INFO] Using worker: aiohttp.GunicornWebWorker
[pulp_content] | [2025-10-13 18:55:58 +0000] [12] [INFO] Booting worker with pid: 12
[pulp_content] | [2025-10-13 18:55:58 +0000] [14] [INFO] Booting worker with pid: 14
This happens with SELinux enforcing and also in permissive mode.
To Reproduce
This is executed on an AlmaLinux9 system, using the docker images from docker.io.
pip install podman-compose
git clone git@github.com:pulp/pulp-oci-images.git
cd pulp-oci-images/images/compose
podman-compose up
Expected behavior
Container stack starts up, and I can run curl localhost:8080/pulp/api/v3/status/ successfully.
Additional context
I'm just getting started with pulp and set up a VM to play around with its feature set.
On the other hand, running the single-container approach worked right away.
So I might be doing something wrong here.