mongo images need to support auth in config files

[sdanieru]

Our current setup for both production and dev deployments specify ssl parameters in a mongod.conf file; this is a common configuration approach and is endorsed by mongodb. Your recent changes to entrypoint.sh break backwards compatibility with any setups that use auth parameters in a config file. Specifically your check to connect to the db isn't compatible with auth specified in the config file.

We were lucky to pull one of your new images for a dev deployment and after investigation, discovered why the image was immediately shutting down after startup, but if we had deployed these images for our production systems, they all would have failed and we wouldn't have known why.

Since these are the 'official' mongo images on dockerhub, it seems reasonable that they support standard configuration: storing ssl and other auth parameters in config files. We sincerely hope that you restore support for this functionality.

At the very least, you should put a prominent warning in your documentation that the images in their current state do not support supplying auth/ssl params in config files.

[sdanieru]

Hey guys|gals,
I don't know when this changed, but I'm now able to launch mongo containers with ssl params defined in the conf file, not on the command line - wonderful! Was conf file parsing added? Can someone else confirm this is working for them as well?

[yvanwangl]

@sdanieru Do you mind to tell me how to launch container with ssl params use conf file. Thank you 👍

[tianon]

@sdanieru the change that was made was to only run our new initdb functionality if it's requested via environment variables (plus some additional detection for when the database is already initialized)

Additionally, there's currently a warning printed during the startup if --config is specified (since it causes exactly the issues you've described with our current solution, which is why #189 is still open and the initdb options aren't documented yet).

I've also got some in-progress changes to fix even that so that --config and our initdb behavior can be used together.

[tianon]

See #183 for the exact PR which probably fixed this for your environment.