Allow all IPs for local atlas deployments
Hello,
we want to create a docker container which runs the atlas-cli with --type local, the base is the official mongodb/atlas docker image. We need this so we can work with atlas-search. The access list which can be provided during deployment setup, is not passed down to the mongod config and we get blocked. A reverse proxy doesn't help in this case. If we enter the final podman image and modify the config, we can't restart the server without crashing the container and which breaks again.
We would really appreciate it if we could somehow get bind IPs activated.
Thank you very much and kind regards!
Kevin
shared this idea
-
AdminJakub
(Admin, MongoDB)
commented
Hi Kevin,
Just wanted to let you know that we have recently released Atlas CLI v1.14.0 that introduces a new flag for "atlas deployments setup" - "--bindIpAll" that addresses your request. We have also published a more detailed guide on how to run Local Atlas experience on Docker. Feel free to check it out here: https://www.mongodb.com/docs/atlas/cli/stable/atlas-cli-deploy-docker/
I'd love to hear your feedback on that expanded solution. Feel free to reach out to me directly or raise a new feedback on the portal.
Thank you,
Jakub -
Kevin
commented
Hi Jakub,
Thank you very much for your response!
Because we want to open the IP range, we went inside the mongo podman container and tried to modify the mongo config because the access list doesn't help. To apply the changes you need to restart mongo but this will kill the container (that was kind of expected to happen). In our docker setup we got so far that we get blocked by the mongo itself (we have podman inside docker running).
I will continue then following the commits and hopefully we can soonish get a setup running to start working with atlas search.
Best regards
Kevin -
AdminJakub
(Admin, MongoDB)
commented
Hi Kevin,
Thank you for raising this request.
With the Public Preview release of the Local Development experience for Atlas, Atlas Search and Vector Search we provide a limited support options for various setups. Running the Local Development via Docker is one of these limitations. However, it's on top of our priority list for next iteration.In meantime you've mentioned:
> If we enter the final podman image and modify the config, we can't restart the server without crashing the container and which breaks again.
What do you mean by "without crashing the container"? What exact steps are you taking to modify the Podman's configuration?Thanks,
Jakub