MongoDB in Azure Container Apps

Question

MongoDB in Azure Container Apps

Rishab Mehta 85

Hello, I need to run MongoDB as an Azure Container App, and I have a couple questions.

How do I ensure that the data doesn't disappear if the container goes down? I saw people saying to connect a file storage system, but if that is the answer does anyone have some examples/tutorials on how to do so?

If I have other containers running in Azure, how do I allow them to connect with the MongoDB container?

Thanks for the help!

Ranashekar Guda 2,905 Reputation points Moderator

2025-02-14T13:18:22.9866667+00:00

Hi @Rishab Mehta,
Following up to see if you have chance to check my previous response and help us with requested information to check and assist you further on this.

Answer accepted by question author

0 additional answers

Your answer

Ranashekar Guda 2,905 Reputation points Moderator

2025-02-14T13:18:22.9866667+00:00

Hi @Rishab Mehta,
Following up to see if you have chance to check my previous response and help us with requested information to check and assist you further on this.

Answer 1

Ranashekar Guda 2,905 Moderator

Hi @Rishab Mehta,
Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.
To run MongoDB as an Azure Container App while ensuring data persistence and enabling connectivity with other containers, follow these steps:

1)Ensuring Data Persistence:

Create an Azure Storage Account and a file share.
Mount the Azure File Share to your MongoDB container to store data outside the container, ensuring persistence even if the container restarts or crashes.
Ensure your MongoDB configuration points to the mounted volume for data storage (e.g., /data/db).

2)Connecting Other Containers to MongoDB:

Deploy your MongoDB container and other containers within the same Azure Container App environment or virtual network to allow them to communicate.
Ensure that the MongoDB container exposes the default port (27017) so that other containers can connect to it.
Use the MongoDB container's service name in connection strings from other containers. Azure Container Apps supports built-in service discovery for easy connection using the container name.

For additional clarification, please refer to the following documentations:

https://learn.microsoft.com/en-us/azure/container-apps/

https://learn.microsoft.com/en-us/azure/container-apps/networking?tabs=workload-profiles-env%2Cazure-cli

I hope this helps! Let me know if you have any further questions or need additional assistance.

Ranashekar Guda 2,905 Reputation points Moderator

2025-02-17T12:24:11.3066667+00:00

Hi @Rishab Mehta,
Following up to see if the above answer was helpful. If this answers your query, do click Accept Answer and YES for was this answer helpful. And, if you have any further query do let us know.
Dylan 20 Reputation points

2025-05-20T16:56:51.42+00:00
I was able to get this working with an important tweak.

At first I was getting errors in the Container App's Log Stream (historical application logs) like this:

2025-05-20T16:14:33.6777847Z stdout F {"t":{"$date":"2025-05-20T16:14:33.677+00:00"},"s":"E", "c":"WT", "id":22435, "ctx":"initandlisten","msg":"WiredTiger error message","attr":{"error":17,"message":{"ts_sec":1747757673,"ts_usec":677434,"thread":"1:0x7ec789d30680","session_name":"connection","category":"WT_VERB_DEFAULT","category_id":12,"verbose_level":"ERROR","verbose_level_id":-3,"msg":"__posix_open_file:924:/data/db/WiredTiger.wt: handle-open: open","error_str":"File exists","error_code":17}}}

The solution I used was to set the mount options on the Container App's volume I was using to store mongo's data to uid=999,gid=999. That is the user id and group id of the mongodb user.

I learned about this solution from this github issue: https://github.com/docker-library/mongo/issues/328#issuecomment-516501046

Share via

MongoDB in Azure Container Apps

0 additional answers

Your answer