-
Notifications
You must be signed in to change notification settings - Fork 16
Description
Describe the bug
Following the quickstart guide, running the docker compose step shows the following failed container:
✘ Container bss-init service "bss-init" didn't complete successfully: exit 1'
Checking the logs show:
[root@openchami-server quickstart]# docker ps -a
6df92de97d5c ghcr.io/openchami/bss:v1.32.0 "/usr/local/bin/bss-…" 16 minutes ago Exited (1) 45 seconds ago bss-init
[root@openchami-server quickstart]# docker logs 6df92de97d5c
This program can only be run on AMD64 processors with v3 microarchitecture support.
I'm testing OpenCHAMI in a VM on an AMD Opteron 6386 SE system.
Steps to reproduce
Follow the quickstart guide to the step docker compose -f base.yml -f postgres.yml -f jwt-security.yml -f haproxy-api-gateway.yml -f openchami-svcs.yml -f autocert.yml -f configurator.yml up -d
Relevant log output
[root@openchami-server quickstart]# docker compose -f base.yml -f postgres.yml -f jwt-security.yml -f haproxy-api-gateway.yml -f openchami-svcs.yml -f autocert.yml -f configurator.yml up -d
[+] Running 13/13
✔ Container postgres Healthy 2.5s
✔ Container opaal-idp Healthy 1.5s
✔ Container step-ca Healthy 0.5s
✔ Container hydra Healthy 1.5s
✔ Container opaal Healthy 2.5s
✔ Container smd Healthy 2.5s
✔ Container configurator Running 0.0s
✔ Container hydra-migrate Exited 1.0s
✔ Container foobar.openchami.cluster Exited 5.0s
✘ Container bss-init service "bss-init" didn't complete successfully: exit 1 2.0s
✔ Container smd-init Exited 1.5s
✔ Container cloud-init Started 0.4s
✔ Container acme-deploy Started 0.4sCode of Conduct
- I agree to follow this project's Code of Conduct