-
Notifications
You must be signed in to change notification settings - Fork 432
Add support for read-only config file mounts #369
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
Conversation
This is a pretty common use-case given that as of Kubernetes v1.9.4 configMaps are mounted as read-only. Fixes docker-library#368
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It still seems odd to me for users to provide a read-only config file and then expect environment variables to change the config, but LGTM.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree it's odd that folks are providing a config file and also providing the environment variables that request we write changes to the config file, but it does appear to be a common enough misunderstanding that this seems like a reasonable workaround.
I'm fully on board with deprecating most of this script for RabbitMQ 3.9+.
Changes: - docker-library/rabbitmq@9effc7f: Update to 3.8.5, Erlang/OTP 23.0.2, OpenSSL 1.1.1g - docker-library/rabbitmq@a5cccf2: Merge pull request docker-library/rabbitmq#369 from st3v/master - docker-library/rabbitmq@34ed62c: touch config file to verify it is read-only
This is a pretty common use-case given that as of Kubernetes v1.9.4 configMaps are mounted as read-only. See #368 for more details.
Consider this PR as a suggestion for one potential fix. There are probably other ways to address this. I'm not too set on how we address it as long as we do so in the docker image. 😊
Fixes #368