Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to launch docker compose stack #647

Open
dot-mike opened this issue Jul 8, 2024 · 2 comments
Open

Unable to launch docker compose stack #647

dot-mike opened this issue Jul 8, 2024 · 2 comments
Assignees

Comments

@dot-mike
Copy link

dot-mike commented Jul 8, 2024

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:

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

[+] Running 9/9
 ✔ Container compose-redis-1                      Healthy                                                                                    7.5s
 ✔ Container compose-postgres-1                   Healthy                                                                                    7.5s
 ✔ Container compose-set_init_password_service-1  Exited                                                                                     9.5s
 ✔ Container compose-migration_service-1          Exited                                                                                     7.5s
 ✔ Container compose-pulp_content-1               Running                                                                                    0.0s
 ✔ Container compose-pulp_content-2               Running                                                                                    0.0s
 ✘ Container compose-signing_key_service-1        service "signing_key_service" didn't complete...                                          12.6s
 ✔ Container compose-pulp_worker-1                Running                                                                                    0.0s
 ✔ Container compose-pulp_worker-2                Running                                                                                    0.0s
service "signing_key_service" didn't complete successfully: exit 1

To Reproduce
Steps to reproduce the behavior:
Follow the documentation (note that the docs uses outdated docker-compose which is not supported)

git clone [email protected]:pulp/pulp-oci-images.git
cd images/compose
docker-compose up

Expected behavior
I expect the stack to be running after running docker compose up and NOT crash / stop unexpectedly.

@MindTooth
Copy link

I experience this myself too:

$ docker compose up
...
signing_key_service-1        | /usr/bin/add_signing_service.sh: line 6: PULP_SIGNING_KEY_FINGERPRINT: unbound variable
service "signing_key_service" didn't complete successfully: exit 1
...

@mikedep333
Copy link
Member

Thank you for reporting this. We plan to work on it fairly soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Status: In Progress
Development

Successfully merging a pull request may close this issue.

4 participants