My docker-compose looks like this:
version: \'3.2\'
services:
mq:
hostname: ${HOST_NAME}
ports:
- \"5671:5671\"
- \"5672:5672\"
- \"1
I recently faced the same issue with rabbitmq:3.7.8-management
image.
I was able to work-around the issue by providing advanced.config
instead of rabbitmq.conf
.
advanced.config
uses a legacy Erlang format, other than that, it worked perfectly for me.
I also provided RABBITMQ_*
environment variables, so it's not an issue.
In my case I was creating a cluster, but I believe the solution is relevant for all use-cases for now until rabbitmq.conf
becomes available.