You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Starting the docker compose stack as per documentation with the command docker compose up results in a crash with code:
set_init_password_service-1 exited with code 0
Gracefully stopping... (press Ctrl+C again to force)
service "signing_key_service" didn't complete successfully: exit 1
checking the logs for the container signing_key_service
$ docker logs 476042309d92
Waiting on postgresql to start...
Postgres started.
Checking for database migrations
Database migrated!
/usr/bin/add_signing_service.sh: line 6: PULP_SIGNING_KEY_FINGERPRINT: unbound variable
Waiting on postgresql to start...
Postgres started.
Checking for database migrations
Database migrated!
/usr/bin/add_signing_service.sh: line 6: PULP_SIGNING_KEY_FINGERPRINT: unbound variable
Running the container stack again with docker compose up -d to start the stack in the background results service signing_key_service not being able to start
Version
Latest version from Git repository
Describe the bug
Starting the docker compose stack as per documentation with the command
docker compose up
results in a crash with code:checking the logs for the container
signing_key_service
Running the container stack again with
docker compose up -d
to start the stack in the background results servicesigning_key_service
not being able to startTo Reproduce
Steps to reproduce the behavior:
Follow the documentation (note that the docs uses outdated
docker-compose
which is not supported)Expected behavior
I expect the stack to be running after running
docker compose up
and NOT crash / stop unexpectedly.The text was updated successfully, but these errors were encountered: