Account for more edge cases in entrypoint scripts #167
Conversation
Not sure what to do about `--config`, since that makes things a _lot_ more complicated to handle properly, but this at least allows users to still specify things like `--port` and not break initdb.
|
Not sure what to do about the users with a config file that specifies ssl key files but then we turn off ssl through the flags for the short init part and mongo fails to start. They can work around it by skipping the entrypoint, but lose the init user creation and chown. $ docker run -d --user mongo --entrypoint mongod mongo:3.4 --config /path/to/mongo.conf |
|
Yeah, I'm not sure either, especially since the config file is a really irritatingly structured YAML, hence |
|
(In other words, this is still better than what we've got now -- our alternative is to back out of the |
|
I guess add a warning to the docs along with the new initialization variables and information. We could also do versions that don't do initialization scripts or user creation? |
|
Wouldn't that be easier to just add an environment variable for, or to show users how to use |
- `drupal`: 8.3.0 (docker-library/drupal#78), remove 8.2 (docker-library/drupal#80) - `ghost`: add `alpine` variant (docker-library/ghost#55) - `mongo`: more edge cases (docker-library/mongo#167, docker-library/mongo#169) - `postgres`: adjust append (docker-library/postgres#270) - `rabbitmq`: add `vm_memory_high_watermark` support based on cgroup limits (docker-library/rabbitmq#105) - `rocket.chat`: 0.55.0-rc.1 - `wordpress`: add `wp-cli` variant (docker-library/wordpress#198)
Not sure what to do about
--config, since that makes things a lot more complicated to handle properly, but this at least allows users to still specify things like--portand not break initdb.