mongo: Cannot configure replica sets with entrypoint-initdb
I’m trying to create simple replicaset enabled images using these docker images. @yosifkit had a suggestion in another thread that this can be done by calling rs.initiate() in a /docker-entrypoint-initdb.d/ script.
However if I do this I get the following:
2019-03-26T12:30:25.889+0000 I COMMAND [conn2] initiate : no configuration specified. Using a default configuration for the set
2019-03-26T12:30:25.889+0000 I COMMAND [conn2] created this configuration for initiation : { _id: "rs0", version: 1, members: [ { _id: 0, host: "127.0.0.1:27017" } ] }
The problem here is that since the init script binds only to localhost, the replicaset has the wrong hostname.
If I call rs.initiate() after initialization phase I get the following:
2019-03-26T12:32:16.792+0000 I COMMAND [conn1] initiate : no configuration specified. Using a default configuration for the set
2019-03-26T12:32:16.793+0000 I COMMAND [conn1] created this configuration for initiation : { _id: "rs0", version: 1, members: [ { _id: 0, host: "mongo:27017" } ] }
This time with the correct hostname.
Is there some way we can resolve this paradox? Either by running a script after the real startup? Or by binding to the proper interfaces during initialisation? Or by forcing the mongo server to accept a replicaset config even if it cannot resolve itself?
Thanks!
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Reactions: 9
- Comments: 23 (2 by maintainers)
The
docker-entrypoint-initdb.dscripts run during an initialization period (and only if the database is empty), during which the container is only listening on localhost so trying to initiate a cluster during that period isn’t possible as it won’t resolve it’s own container hostname.So you’ll probably need some manual intervention after everything is initialized, as using the
docker-entrypoint-initdb.dwill error withreplSet initiate got NodeNotFound: No host described in new configuration 1 for replica set myrepl maps to this node, but then running the samers.initiate()will work afterwardsSomehow, I wrote an ugly hack to initialize replica set by abusing docker-entrypoint-initdb.d. Hope that helps someone coming to this issue.
I’v come up a work-around using
healthcheckinstead ofdocker-entrypoint-initdb.d.Define a js script to detect master status, then do init once if necessary:
In docker-compose, define a healthcheck using the script:
Though this requires further
healthycoordination between services, where compose version3.9is required to supportcondition: service_healthyThank you @matthew-holder-revvity you gave me the fix I needed for a clean docker-compose setup.
I ended up doing the following, using the new config syntax, thus far I think it’s pretty clean.
What a hack @zhangyoufu! I think there needs to be some support for this in the official docker image. There are several features of MongoDB only available with a replica set and this is a common production configuration. So it makes local development hard if we cannot setup a dev db with the same configuration.
For anyone looking for an answer to this in a Compose stack, you can set the
hostnameon the container addextra_hostsfor it to point to127.0.0.1and then reference it in the in entrypoint extra scripts you copy to the container. Just use$(which hostname)to get your container hostname.For anyone looking to the answer, here is a hack that made it working for me. I’ve made a
healthcheck.shscript:and calling that
healthcheck.shscript fromdocker-compose.yml:Alright, I already read https://github.com/docker-library/mongo/blob/master/docker-entrypoint.sh and it appears that only valid case for rs initiation will be mine, no good way to make replica set working with other hardcoded arguments.
Can this be properly documented on docker mongodb page? As this was really confusing and time consuming to dig through.
In order to properly do that (run processes after starting the “real” long-term
mongod), we would need a supervisor-like process and that is not complexity that we want to add or maintain (and is beyond a “simple” bash script).By supervisor process, I mean basically the following:
initdb.dscriptsmongodand scripts both appear in stdout/stderr appropriatelymongodand do something if it exits unexpectedlymongodis “ready”, triggerpost-dbstartupscriptspost-dbstartupscripts fail in any way or if they “never” finishpost-dbstartupscripts?You don’t have to deal with the first 6 if the container is used as-is since that is “free” because of how the image is designed. And then the correct solution is to use your orchestration platform to run something to coordinate the initialization and joining of multiple
mongocontainers.Maybe this can be helpful too https://gist.github.com/zhangyoufu/d1d43ac0fa268cda4dd2dfe55a8c834e#gistcomment-3554586
Hmm - I did miss the “my hurried dockerfile will not actually work” point sorry!
Still I think the idea has merit; but-for the squelching of the
--bind-iparguments this would work just fine, and would have some value for single instance deployment / unit test / many other basic cases. [I realise the whole point of force binding localhost is to ensure nobody can connect until the startup scripts are complete. Not sure how to reconcile that.]If there’s a direction you think would be acceptable and could be made to work I’d be willing to have a go at implementing it.