Rabbit MQ Container Unhealthy

[cbusseata]

Describe the bug I am following the getting started guide to run conductor using docker for the first time. I cannot start the containers, however. I can build the containers, but whenever I try to bring them up, I got a notification about the Rabbit MQ container being unhealthy.

Details Conductor version: latest - here's the most recent commit hash: 8c65ec19727902a434e65f98a0e8074a9748c543 Persistence implementation: default Queue implementation: default Lock: Redis or Zookeeper? default Workflow definition: none Task definition: Event handler definition:

To Reproduce

git clone https://github.com/Netflix/conductor.git
cd conductor/docker
docker-compose build
docker-compose up

Expected behavior I expected the containers to all start up without issues

Screenshots

Additional context I am using an 2021 M1 Macbook Pro

[bwishan]

+1 Also on M1.

No errors indicated in docker logs for the unhealthy container id.

EDIT 02/26 - It appears this was fixed. I was able to rebuild and get things running now.

EDIT 02/26 10:54 AM PT - Looks like this didn't fix it. The health check is failing. Replacing the test with test: rabbitmq-diagnostics -q ping now gets all the containers to start. I haven't yet figured out if the whole thing works yet since this is my first time playing with Conductor.

EDIT 02/26 12:14 PM PT - After playing some more, it seems that there's a regression in v3.13.5 that doesn't work out of the box. Going back to v3.13.3 seems to get things working again. Since I'm running on Apple silicon, I did have to manually update the elasticsearch version (to elasticsearch:8.6.2) in the docker-compose since the old version didn't have a valid arm image. The version of the docker compose file in this tag also doesn't have any of the rabbitmq components included, so that whole problem had just gone away.