// Bitnami alternatives / mongodb

Bitnami MongoDB alternative
Replacing bitnamilegacy/mongodb

The bitnamilegacy/mongodb image has had about 4.1 million pulls since Bitnami moved it to the legacy repository, and it receives no updates. Switching to the official mongo image means changing environment variables and the data path. Get either wrong and the new container starts empty.

Get a drop-in MongoDB image

Trusted globally by enterprises

Henry ScheinEnbridgeGojekMicrosoft

Bitnami MongoDB variables and their official equivalents

Bitnami MongoDB image to official mongo:

SettingBitnamiOfficial image
Root userMONGODB_ROOT_USERMONGO_INITDB_ROOT_USERNAME
Root passwordMONGODB_ROOT_PASSWORDMONGO_INITDB_ROOT_PASSWORD
Initial databaseMONGODB_DATABASEMONGO_INITDB_DATABASE
App userMONGODB_USERNAME / MONGODB_PASSWORDCreate in an init script
Data path/bitnami/mongodb/data/db

What breaks when you switch

  • The official image only creates the root user. Bitnami's app-user variables have to become a script in /docker-entrypoint-initdb.d.
  • Replica set variables (MONGODB_REPLICA_SET_*) have no official equivalent.
  • Official images for MongoDB 5.0 and later need a CPU with AVX, and the image warns at start-up when it is missing.

What happened to the Bitnami MongoDB image

For years, bitnami/mongodb on Docker Hub was one of the most common ways to deploy MongoDB on Kubernetes, usually through the Bitnami MongoDB Helm chart. On 28 August 2025 Broadcom moved every versioned Bitnami container image, including this one, to the bitnamilegacy repository, and removed the public docker.io/bitnami catalog on 29 September 2025. The free tier now offers only latest tags of a limited set of images for development.

The legacy Docker image still pulls, so existing deployments keep working. It no longer receives updates, which means every vulnerability disclosed since the move stays open in the MongoDB binary, in the base image and in every bundled dependency. Container scanners will report a growing count at every audit, and a workload that depends on a frozen public repository is one registry change away from ImagePullBackOff.

How to migrate MongoDB off Bitnami safely

  1. Find every reference to bitnami/mongodb and bitnamilegacy/mongodb in running workloads, Helm values files and CI pipelines, including init containers.
  2. Record the MongoDB version each deployment pins. Versions past upstream end of life are not covered by the free open source images.
  3. Take a backup and test a restore before touching a stateful workload.
  4. Mirror the replacement container images into your own registry, and scan them before you deploy.
  5. Move one replica or one environment at a time, and confirm the data path, file ownership and credentials on the new image.
  6. Remove every remaining legacy reference so nothing falls back to the archive on the next deploy.

Your options

OSSeva drop-in image

A patched image that keeps Bitnami's variables, paths and user, covering MongoDB 4.2 to 6.0, including hardware without AVX. Your chart keeps working after a registry change.

Official mongo image

Free and maintained for current versions. Apply the mapping above and move the volume.

Bitnami Secure Images

Broadcom's paid catalog keeps the Bitnami layout for supported versions, sold within TrueSource.

Repoint the Bitnami MongoDB Helm chart

# values-override.yaml
image:
  registry: registry.example.com   # your mirror of the replacement image
  repository: mongodb
  tag: "<pinned version>"
global:
  security:
    allowInsecureImages: true      # recent Bitnami charts reject non-Bitnami images without this

This works only with an image that keeps Bitnami's layout. With the official image, rewrite the chart or move to an operator. See replacing bitnamilegacy images for the full inventory and rollout steps.

Frequently asked questions

What is the best alternative to the Bitnami MongoDB image?

To keep the Bitnami MongoDB Helm chart unchanged, use a Bitnami-compatible image; OSSeva ships patched ones covering MongoDB 4.2 to 6.0, including hardware without AVX. To rewrite the deployment, use the official mongo image.

Is bitnamilegacy/mongodb still getting security updates?

No. Bitnami moved versioned images to the bitnamilegacy repository on 28 August 2025 and describes it as receiving no further updates. It had about 4.1 million pulls by September 2026.

Can I keep using the Bitnami MongoDB Helm chart?

Yes, with a maintained image that keeps Bitnami's layout. Set image.registry and image.repository in your values file, and set global.security.allowInsecureImages to true, because recent Bitnami charts refuse non-Bitnami images otherwise.

Is Bitnami no longer free?

Not for production. Since 28 August 2025, versioned Bitnami images live in the bitnamilegacy repository with no updates, and the free tier offers latest tags of a limited set of images for development. Maintained, versioned images are sold as Bitnami Secure Images, which Broadcom prices by quote.

Where does the Bitnami MongoDB image store data?

Under /bitnami/mongodb. The official image uses /data/db, so the volume mount must change when you switch images.

Keep your MongoDB chart. Change the image.

Send us your image list and versions; we reply with coverage and a migration plan within five working days.

Book a Discovery CallAll Bitnami alternatives →