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
Following instructions from https://sdx-docs.readthedocs.io/en/latest/sdx_deploy_single_server.html, I did a docker compose up this morning and it failed, seemingly because of a problem with rabbitmq:latest docker image. It would be a good idea to use a release tag instead of latest.
Hi Sajith, I'm testing here with rabbitmq:latest (digest dc6c413c58a5, created 10h ago) and it is working fine for me. Just tested here, making sure to pull the very latest version of each one of the images, and the whole process worked very smoothly.
Personally, I would prefer to stay with rabbitmq:latest unless a major problem happens and we reconsider this. Which does not seems to be the case.
I did a docker pull again, and that pulled the one with digest sha256:d74c576bf9cee66ec28c96299f8cca896945489ee1546fb892edc2116b32e2dc. That seems to run.
I still think that we should prefer a known working version, in the interest of reproducibility.
Following instructions from https://sdx-docs.readthedocs.io/en/latest/sdx_deploy_single_server.html, I did a
docker compose up
this morning and it failed, seemingly because of a problem withrabbitmq:latest
docker image. It would be a good idea to use a release tag instead oflatest
.Here's a section of
docker logs rabbitmq
:The text was updated successfully, but these errors were encountered: