Hardcoded sample credentials in rabbitmq dockerfile make it hard to use in production

[collectoss-issue-migrator]

Note

Migrated from augurlabs/augur#3402
Originally opened by @MoralCode on 2025-11-12

---

https://github.com/chaoss/augur/blob/4732c8090ec76924d6c920c991eedd9e26d73617/docker/rabbitmq/Dockerfile#L8-L10

These lines seem to be causing issues when trying to use the rabbitmq container in a production stack for Augur. Building this container as-is seems to cause the augur container to fail with the following error when connecting to rabbit:

Login was refused using authentication mechanism PLAIN. For details see the broker logfile.

This seems to be because, while the production setup was passing a custom username/password to both rabbit and augur, it seems like rabbit may be preferring its own default credentials from this Dockerfile (which are added at build time, not runtime).

Wanted to file this issue to invite discussion on what the best way to solve this is

[collectoss-issue-migrator]

Note

Migrated comment from original
Originally posted by @MoralCode on 2025-11-21

---

The easy way to test this is to put AUGUR_RABBITMQ_PASSWORD and a custom password in your augur .env, and then take the compose stack down and then back up. i suspect it would cause a connection failure with rabbit

[collectoss-issue-migrator]

Note

Migrated comment from original
Originally posted by @iGufrankhan on 2025-11-23

---

I tested this issue by rebuilding the RabbitMQ image and running Augur both with and without custom credentials.

Results:

• Without any env vars → RabbitMQ correctly used the default credentials (augur).
• With custom values in .env → RabbitMQ correctly used the custom credentials I provided (ironman123).

Verification commands:
docker exec -it augur-rabbitmq-1 rabbitmqctl list_users
rabbitmqadmin list vhosts

Build/run steps I used:
docker-compose down -v
docker-compose build rabbitmq
docker-compose up -d

Everything behaved as expected and there were no authentication errors.

Based on this testing, the issue appears to be resolved. you can confirm through i provide image