-
Notifications
You must be signed in to change notification settings - Fork 429
Please mention RABBITMQ_DEFAULT_USER / RABBITMQ_DEFAULT_PASS in the Readme #526
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This PR docker-library/docs#2012 removed the newly supported variables from the disallowed list. So users would be able to see the complete list of supported variables at https://www.rabbitmq.com/configure.html#supported-environment-variables Seems like their docs weren't updated yet with the new supported variables |
yeah, it's not in the offcial documentation, would be nice if it was updated.
The current Readme does a really good job with the tags, but there is no information to be found regarding credentials, other than a link to a convoluted page which tells you (incorrectly) that the only way to change the password is to mount a config file. I think it would be very helpful to mention these 3 variables in the Readme. |
Available in recent 3.9 and 3.8 patch releases. References docker-library/rabbitmq#508, docker-library/rabbitmq#526, docker-library/docs#2069
FYI: rabbitmq/rabbitmq-website@ec238a2. RabbitMQ docs are open source, so changes similar to the above one can be contributed by anyone ;) |
Why were the environment variables removed? |
I just stumbled upon #508 after I tried to figure out how I can provide a username and password to RabbitMQ 3.9 in a GitLab CI pipeline.
So the Readme says that the use of environment variables to configure RabbitMQ is not possible anymore, but then in rabbitmq-server#3299, support for the variables
RABBITMQ_DEFAULT_VHOST
,RABBITMQ_DEFAULT_USER
andRABBITMQ_DEFAULT_PASS
was added.Can you mention this in the Readme on Dockerhub? There are quite a few situations (like GitHub Actions or GitLab CI) where mounting config files is not an option and it would be nice if the Readme helped with that.
The text was updated successfully, but these errors were encountered: