Create a custom image derived from mongodb/mongodb-atlas-local

hey,

Im trying to create a custom image for our development purposes using the mongodb/mongodb-atlas-local image.
However if my docker entrypoint uses the regular mongo starting command:

mongod --replSet ${REPLICA_SET_NAME} --port ${SERVICE_PORT} --bind_ip_all

I get the following when trying to utilize search index capabilities:

MongoServerError: Using Atlas Search Database Commands and the $listSearchIndexes aggregation stage requires additional configuration. Please connect to Atlas or an AtlasCLI local deployment to enable. For more information on how to connect, see https://dochub.mongodb.org/core/atlas-cli-deploy-local-reqs.

So instead i used this entrypoint /usr/local/bin/runner server however it doesnt expose the settings i need (replica name for example).
how would you do set up the docker given my requirements?

P.S

  • i saw that you can use the atlas cli however this doesnt work with our current dev env ci, we need a custom built docker image.
  • note that in prod/staging/pre we use atlas cloud, so this is for development purposes

Hi @daktak , we’ve designed mongodb/mongodb-atlas-local to be a simple getting-started experience, so we haven’t surfaced these configurations. However, I would be interested to learn more about what exactly you’d like to see exposed (other than replicaset name), and give me a bit more detail about your use case so I can understand what you’re trying to achieve.

The main use so far is the changing of the replica name and the control of the internal container port (as shown in the original mongod command),
I need to use a custom docker image in order to properly set up logging related configs (Data dog etc).
This is all done to align the dev env with the staging and pre/prod env configs (which use atlas mongo via access to atlasses VPC).

Thanks @daktak. This is something we might consider addressing if we see growing interest, so please consider submitting a feature request.

I’ve seeded this similar request already, which you might prefer to upvote this and add a comment for your requirement / use case, otherwise please feel free to submit a new feature request here.