[{"_1":2,"_148":-5,"_149":-5},"loaderData",{"_3":4,"_17":18,"_25":26,"_142":143},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7,"_13":14,"_15":16},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","theme","system","contrast","normal","routes/_layout",{"_19":-5,"_20":21,"_22":21,"_23":11,"_24":21},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","showHoneypotTrap","routes/_layout.layers.$namespace.$reponame.$tag.(images).($imageUrlDigest)",{"_27":28,"_29":30,"_59":60,"_61":-7,"_62":-7,"_63":-7,"_64":-7,"_65":-5,"_66":-5,"_67":11,"_68":11,"_52":69,"_132":21,"_99":100,"_133":98,"_134":51,"_35":36,"_135":11,"_136":21,"_137":138,"_139":-5,"_140":11,"_141":11},"scanningType","none","tagData",{"_31":32,"_33":34,"_35":36,"_37":38,"_39":40,"_41":42,"_43":44,"_45":34,"_46":47,"_48":49,"_50":51,"_52":53,"_54":-5,"_55":44,"_56":57,"_58":21},"content_type","unrecognized","creator",35095401,"digest","sha256:8b0ff2cbbb0822980d2b87144666db474c2457604f9fb4f35526ab6905b06a8e","full_size",8190069,"id",1242639768,"images",[],"last_updated","2026-07-23T02:54:37.33459Z","last_updater","last_updater_username","bitnamibot508","media_type","application/vnd.vmware.tac.metadata.config.v1+json","name","sha256-127db7f492afa5f6952f954d50da536a378784d689ac23d80b359811909596ae.metadata","repository",292444,"tag_last_pulled","tag_last_pushed","tag_status","inactive","v2","tagImages",[],"layerOrdinals","packageName","cveId","sbom","scoutSummary","staticSummary","isScoutPaymentRequired","canSeeVulnerabilities",{"_70":71,"_82":83,"_85":86,"_87":88,"_89":11,"_43":90,"_91":92,"_93":94,"_50":98,"_99":100,"_101":102,"_103":84,"_104":105,"_106":107,"_108":109,"_110":-5,"_111":112,"_113":114,"_115":11,"_116":100,"_117":118,"_123":21,"_124":125,"_129":100,"_130":131},"categories",[72,76,79],{"_50":73,"_74":75},"Integration & delivery","slug","integration-and-delivery",{"_50":77,"_74":78},"Internet of things","internet-of-things",{"_50":80,"_74":81},"Databases & storage","databases-and-storage","content_types",[84,32],"image","date_registered","2015-08-19T17:55:56.569199Z","description","Bitnami Secure Image for mongodb","is_private","2026-09-30T14:19:25.150484Z","last_modified","2026-09-22T08:06:29.820806Z","media_types",[95,96,97,49],"application/vnd.docker.distribution.manifest.list.v2+json","application/vnd.oci.image.config.v1+json","application/vnd.oci.image.index.v1+json","mongodb","namespace","bitnami","pull_count",1736507350,"repository_type","star_count",267,"status",1,"status_description","active","source","collaborator_count",0,"full_description","# MongoDB® packaged by Bitnami\n\n> MongoDB® is a relational open source NoSQL database. Easy to use, it stores data in JSON-like documents. Automated scalability and high-performance. Ideal for developing cloud native applications.\n\n[Overview of MongoDB®](https://www.mongodb.org)\nDisclaimer: The respective trademarks mentioned in the offering are owned by the respective companies. We do not provide a commercial license for any of these products. This listing has an open-source license. MongoDB(R) is run and maintained by MongoDB, which is a completely separate project from Bitnami.\n\n## TL;DR\n\n```console\ndocker run --name mongodb REGISTRY_NAME/bitnami/mongodb:latest\n```\n\n> Note: You need to substitute the `REGISTRY_NAME` placeholder with a reference to your container registry.\n\n## Using `docker-compose.yml`\n\nThe docker-compose.yaml file of this container can be found in the [Bitnami Containers repository](https://github.com/bitnami/containers/).\n\n[https://github.com/bitnami/containers/tree/main/bitnami/mongodb/docker-compose.yml](https://github.com/bitnami/containers/tree/main/bitnami/mongodb/docker-compose.yml)\n\nPlease be aware this file has not undergone internal testing. Consequently, we advise its use exclusively for development or testing purposes. For production-ready deployments, we highly recommend utilizing its associated [Bitnami Helm chart](https://github.com/bitnami/charts/tree/main/bitnami/mongodb).\n\n## How to deploy MongoDB® in Kubernetes?\n\nDeploying Bitnami applications as Helm Charts is the easiest way to get started with our applications on Kubernetes. Read more about the installation in the [Bitnami MongoDB® Chart GitHub repository](https://github.com/bitnami/charts/tree/master/bitnami/mongodb).\n\n## Why use a non-root container?\n\nNon-root container images add an extra layer of security and are generally recommended for production environments. However, because they run as a non-root user, privileged tasks are typically off-limits. Learn more about non-root containers [in our docs](https://techdocs.broadcom.com/us/en/vmware-tanzu/application-catalog/tanzu-application-catalog/services/tac-doc/apps-tutorials-work-with-non-root-containers-index.html).\n\n## Supported tags and respective `Dockerfile` links\n\nLearn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags [in our documentation page](https://techdocs.broadcom.com/us/en/vmware-tanzu/application-catalog/tanzu-application-catalog/services/tac-doc/apps-tutorials-understand-rolling-tags-containers-index.html).\n\n## Get this image\n\nThe Bitnami MongoDB® Docker image is only available to [Bitnami Secure Images](https://bitnami.com) customers.\n\n## Persisting your database\n\nIf you remove the container all your data will be lost, and the next time you run the image the database will be reinitialized. To avoid this loss of data, you should mount a volume that will persist even after the container is removed.\n\nFor persistence you should mount a directory at the `/bitnami/mongodb` path. If the mounted directory is empty, it will be initialized on the first run.\n\n> **NOTE** As this is a non-root container, the mounted files and directories must have the proper permissions for the UID `1001`.\n\n## Connecting to other containers\n\nUsing [Docker container networking](https://docs.docker.com/engine/userguide/networking/), a MongoDB® server running inside a container can easily be accessed by your application containers.\n\nContainers attached to the same network can communicate with each other using the container name as the hostname.\n\n## Configuration\n\nThe following section describes the supported environment variables\n\n### Environment variables\n\nThe following tables list the main variables you can set.\n\n#### Customizable environment variables\n\n| Name | Description | Default Value |\n|-----------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------|\n| `MONGODB_MOUNTED_CONF_DIR` | Directory for including custom configuration files (that override the default generated ones) | `${MONGODB_VOLUME_DIR}/conf` |\n| `MONGODB_INIT_RETRY_ATTEMPTS` | Maximum retries for checking the service initialization status | `7` |\n| `MONGODB_INIT_RETRY_DELAY` | Time (in seconds) to wait between retries for checking the service initialization status | `5` |\n| `MONGODB_PORT_NUMBER` | MongoDB port | `$MONGODB_DEFAULT_PORT_NUMBER` |\n| `MONGODB_EXTRA_FLAGS` | Extra flags for MongoDB initialization | `nil` |\n| `MONGODB_ENABLE_NUMACTL` | Execute commands using numactl | `false` |\n| `MONGODB_SHELL_EXTRA_FLAGS` | Extra flags when using the mongodb client during initialization (useful when mounting init scripts) | `nil` |\n| `MONGODB_ADVERTISED_HOSTNAME` | Hostname to use for advertising the MongoDB service | `nil` |\n| `MONGODB_ADVERTISE_IP` | Whether advertised hostname is set to container ip | `false` |\n| `MONGODB_ADVERTISED_PORT_NUMBER` | MongoDB advertised port number. It is recommended to pass this environment variable if you have a proxy port forwarding requests to container. | `nil` |\n| `MONGODB_DISABLE_JAVASCRIPT` | Disable MongoDB server-side javascript execution | `no` |\n| `MONGODB_ENABLE_JOURNAL` | Enable MongoDB journal | `nil` |\n| `MONGODB_DISABLE_SYSTEM_LOG` | Disable MongoDB daemon system log | `nil` |\n| `MONGODB_ENABLE_DIRECTORY_PER_DB` | Use a separate folder for storing each database data | `nil` |\n| `MONGODB_ENABLE_IPV6` | Use IPv6 for database connections | `nil` |\n| `MONGODB_SYSTEM_LOG_VERBOSITY` | MongoDB daemon log level | `nil` |\n| `MONGODB_ROOT_USER` | User name for the MongoDB root user | `root` |\n| `MONGODB_ROOT_PASSWORD` | Password for the MongoDB root user | `nil` |\n| `MONGODB_USERNAME` | User to generate at initialization time | `nil` |\n| `MONGODB_PASSWORD` | Password for the non-root user specified in MONGODB_USERNAME | `nil` |\n| `MONGODB_DATABASE` | Name of the database to create at initialization time | `nil` |\n| `MONGODB_METRICS_USERNAME` | User used for metrics collection, for example with mongodb_exporter | `nil` |\n| `MONGODB_METRICS_PASSWORD` | Password for the non-root user specified in MONGODB_METRICS_USERNAME | `nil` |\n| `MONGODB_EXTRA_USERNAMES` | Comma or semicolon separated list of extra users to be created. | `nil` |\n| `MONGODB_EXTRA_PASSWORDS` | Comma or semicolon separated list of passwords for the users specified in MONGODB_EXTRA_USERNAMES. | `nil` |\n| `MONGODB_EXTRA_DATABASES` | Comma or semicolon separated list of databases to create at initialization time for the users specified in MONGODB_EXTRA_USERNAMES. | `nil` |\n| `ALLOW_EMPTY_PASSWORD` | Permit accessing MongoDB without setting any password | `no` |\n| `MONGODB_REPLICA_SET_MODE` | MongoDB replica set mode. Can be one of primary, secondary or arbiter | `nil` |\n| `MONGODB_REPLICA_SET_NAME` | Name of the MongoDB replica set | `$MONGODB_DEFAULT_REPLICA_SET_NAME` |\n| `MONGODB_REPLICA_SET_KEY` | MongoDB replica set key | `nil` |\n| `MONGODB_INITIAL_PRIMARY_HOST` | Hostname of the replica set primary node (necessary for arbiter and secondary nodes) | `nil` |\n| `MONGODB_INITIAL_PRIMARY_PORT_NUMBER` | Port of the replica set primary node (necessary for arbiter and secondary nodes) | `27017` |\n| `MONGODB_INITIAL_PRIMARY_ROOT_PASSWORD` | Primary node root user password (necessary for arbiter and secondary nodes) | `nil` |\n| `MONGODB_INITIAL_PRIMARY_ROOT_USER` | Primary node root username (necessary for arbiter and secondary nodes) | `root` |\n| `MONGODB_SET_SECONDARY_OK` | Mark node as readable. Necessary for cases where the PVC is lost | `no` |\n| `MONGODB_DISABLE_ENFORCE_AUTH` | By default, MongoDB authentication will be enforced. If set to true, MongoDB will not enforce authentication | `false` |\n\n#### Read-only environment variables\n\n| Name | Description | Value |\n|-------------------------------------------|------------------------------------------------------------------------|-------------------------------------------|\n| `MONGODB_VOLUME_DIR` | Persistence base directory | `$BITNAMI_VOLUME_DIR/mongodb` |\n| `MONGODB_BASE_DIR` | MongoDB installation directory | `$BITNAMI_ROOT_DIR/mongodb` |\n| `MONGODB_CONF_DIR` | MongoDB configuration directory | `$MONGODB_BASE_DIR/conf` |\n| `MONGODB_DEFAULT_CONF_DIR` | MongoDB default configuration directory | `$MONGODB_BASE_DIR/conf.default` |\n| `MONGODB_LOG_DIR` | MongoDB logs directory | `$MONGODB_BASE_DIR/logs` |\n| `MONGODB_DATA_DIR` | MongoDB data directory | `${MONGODB_VOLUME_DIR}/data` |\n| `MONGODB_TMP_DIR` | MongoDB temporary directory | `$MONGODB_BASE_DIR/tmp` |\n| `MONGODB_BIN_DIR` | MongoDB executables directory | `$MONGODB_BASE_DIR/bin` |\n| `MONGODB_TEMPLATES_DIR` | Directory where the mongodb.conf template file is stored | `$MONGODB_BASE_DIR/templates` |\n| `MONGODB_MONGOD_TEMPLATES_FILE` | Path to the mongodb.conf template file | `$MONGODB_TEMPLATES_DIR/mongodb.conf.tpl` |\n| `MONGODB_CONF_FILE` | Path to MongoDB configuration file | `$MONGODB_CONF_DIR/mongodb.conf` |\n| `MONGODB_KEY_FILE` | Path to the MongoDB replica set keyfile | `$MONGODB_CONF_DIR/keyfile` |\n| `MONGODB_DB_SHELL_FILE` | Path to MongoDB dbshell file | `/.dbshell` |\n| `MONGODB_RC_FILE` | Path to MongoDB rc file | `/.mongorc.js` |\n| `MONGOSH_DIR` | Path to mongosh directory | `/.mongodb` |\n| `MONGOSH_RC_FILE` | Path to mongosh rc file | `/.mongoshrc.js` |\n| `MONGODB_PID_FILE` | Path to the MongoDB PID file | `$MONGODB_TMP_DIR/mongodb.pid` |\n| `MONGODB_LOG_FILE` | Path to the MongoDB log file | `$MONGODB_LOG_DIR/mongodb.log` |\n| `MONGODB_INITSCRIPTS_DIR` | Path to the MongoDB container init scripts directory | `/docker-entrypoint-initdb.d` |\n| `MONGODB_DAEMON_USER` | MongoDB system user | `mongo` |\n| `MONGODB_DAEMON_GROUP` | MongoDB system group | `mongo` |\n| `MONGODB_DEFAULT_PORT_NUMBER` | MongoDB port set at build time | `27017` |\n| `MONGODB_DEFAULT_ENABLE_JOURNAL` | Enable MongoDB journal at build time | `true` |\n| `MONGODB_DEFAULT_DISABLE_SYSTEM_LOG` | Disable MongoDB daemon system log set at build time | `false` |\n| `MONGODB_DEFAULT_ENABLE_DIRECTORY_PER_DB` | Use a separate folder for storing each database data set at build time | `false` |\n| `MONGODB_DEFAULT_ENABLE_IPV6` | Use IPv6 for database connections set at build time | `false` |\n| `MONGODB_DEFAULT_SYSTEM_LOG_VERBOSITY` | MongoDB daemon log level set at build time | `0` |\n| `MONGODB_DEFAULT_REPLICA_SET_NAME` | Name of the MongoDB replica set at build time | `replicaset` |\n\n### Initializing a new instance\n\nWhen the container is executed for the first time, it will execute the files with extensions `.sh`, and `.js` located at `/docker-entrypoint-initdb.d`.\n\nIn order to have your custom files inside the docker image you can mount them as a volume.\n\n### Passing extra command-line flags to mongod startup\n\nPassing extra command-line flags to the mongod service command is possible through the following env var:\n\n- `MONGODB_EXTRA_FLAGS`: Flags to be appended to the `mongod` startup command. No defaults\n- `MONGODB_CLIENT_EXTRA_FLAGS`: Flags to be appended to the `mongo` command which is used to connect to the (local or remote) `mongod` daemon. No defaults\n\n### Configuring system log verbosity level\n\nConfiguring the system log verbosity level is possible through the following env vars:\n\n- `MONGODB_DISABLE_SYSTEM_LOG`: Whether to enable/disable system log on MongoDB®. Default: `false`. Possible values: `[true, false]`.\n- `MONGODB_SYSTEM_LOG_VERBOSITY`: MongoDB® system log verbosity level. Default: `0`. Possible values: `[0, 1, 2, 3, 4, 5]`. For more information about the verbosity levels please refer to the [MongoDB® documentation](https://docs.mongodb.com/manual/reference/configuration-options/#systemLog.verbosity)\n\n### Using numactl\n\n In order to enable launching commands using numactl, set the `MONGODB_ENABLE_NUMACTL` variable to true. For more information on this, check the official [MongoDB documentation][()\n\n### Enabling/disabling IPv6\n\nEnabling/disabling IPv6 is possible through the following env var:\n\n- `MONGODB_ENABLE_IPV6`: Whether to enable/disable IPv6 on MongoDB®. Default: `false`. Possible values: `[true, false]`\n\n### Enabling/disabling directoryPerDB\n\nEnabling/disabling [directoryPerDB](https://docs.mongodb.com/manual/reference/configuration-options/#storage.directoryPerDB) is possible through the following env var:\n\n- `MONGODB_ENABLE_DIRECTORY_PER_DB`: Whether to enable/disable directoryPerDB on MongoDB®. Default: `true`. Possible values: `[true, false]`\n\n### Enabling/disabling journaling\n\nEnabling/disabling [journal](https://docs.mongodb.com/manual/reference/configuration-options/#mongodb-setting-storage.journal.enabled) is possible through the following env var:\n\n- `MONGODB_ENABLE_JOURNAL`: Whether to enable/disable journaling on MongoDB®. Default: `true`. Possible values: `[true, false]`\n\n### Setting the root user and password on first run\n\nPassing the `MONGODB_ROOT_PASSWORD` environment variable when running the image for the first time will set the password of `MONGODB_ROOT_USER` to the value of `MONGODB_ROOT_PASSWORD` and enable authentication on the MongoDB® server. If unset, `MONGODB_ROOT_USER` defaults to `root`.\n\nThe `MONGODB_ROOT_USER` user is configured to have full administrative access to the MongoDB® server. When `MONGODB_ROOT_PASSWORD` is not specified the server allows unauthenticated and unrestricted access.\n\n### Creating a user and database on first run\n\nYou can create a user with restricted access to a database while starting the container for the first time. To do this, provide the `MONGODB_USERNAME`, `MONGODB_PASSWORD` and `MONGODB_DATABASE` environment variables.\n\n> **NOTE** Creation of a user enables authentication on the MongoDB® server and as a result unauthenticated access by *any* user is not permitted.\n\n### Setting up replication\n\nA [replication](https://docs.mongodb.com/manual/replication/) cluster can easily be setup with the Bitnami MongoDB® Docker Image using the following environment variables:\n\n- `MONGODB_REPLICA_SET_MODE`: The replication mode. Possible values `primary`/`secondary`/`arbiter`. No defaults.\n- `MONGODB_REPLICA_SET_NAME`: MongoDB® replica set name. Default: **replicaset**\n- `MONGODB_PORT_NUMBER`: The port each MongoDB® will use. Default: **27017**\n- `MONGODB_INITIAL_PRIMARY_HOST`: MongoDB® initial primary host, once the replicaset is created any node can be eventually promoted to be the primary. No defaults.\n- `MONGODB_INITIAL_PRIMARY_PORT_NUMBER`: MongoDB® initial primary node port, as seen by other nodes. Default: **27017**\n- `MONGODB_ADVERTISED_HOSTNAME`: MongoDB® advertised hostname. No defaults. It is recommended to pass this environment variable if you experience issues with ephemeral IPs. Setting this env var makes the nodes of the replica set to be configured with a hostname instead of the machine IP.\n- `MONGODB_ADVERTISE_IP`: MongoDB® advertised hostname is set to container ip. Default: **false**. Overrides `MONGODB_ADVERTISED_HOSTNAME`\n- `MONGODB_ADVERTISED_PORT_NUMBER`: MongoDB® advertised port number. No defaults. It is recommended to pass this environment variable if you have a proxy port forwarding requests to container.\n- `MONGODB_REPLICA_SET_KEY`: MongoDB® replica set key. Length should be greater than 5 characters and should not contain any special characters. Required for all nodes. No default.\n- `MONGODB_ROOT_USER`: MongoDB® root user name. Default: **root**.\n- `MONGODB_ROOT_PASSWORD`: MongoDB® root password. No defaults. Only for primary node.\n- `MONGODB_INITIAL_PRIMARY_ROOT_PASSWORD`: MongoDB® initial primary root password. No defaults. Only for secondaries and arbiter nodes.\n\nIn a replication cluster you can have one primary node, zero or more secondary nodes and zero or one arbiter node.\n\n> **NOTE**: The total number of nodes on a replica set scenario cannot be higher than 8 (1 primary, 6 secondaries and 1 arbiter)\n\n#### How is a replica set configured?\n\nThere are four different roles in a replica set configuration (primary, secondary, hidden or arbiter). Each one of these roles are configured in a different way:\n\n**Primary node configuration:**\n\nThe replica set is started with the `rs.initiate()` command and some configuration options to force the primary to be the primary. Basically, the priority is increased from the default (1) to 5.\nTo verify the primary is actually the primary we validate it with the `db.isMaster().ismaster` command.\n\nThe primary node has a volume attached so the data is preserved between deployments as long as the volume exists.\n\nIn addition, the primary node initialization script will check for the existence of a `.initialized` file in the `/bitnami/mongodb` folder to discern whether it should create a new replica set or on the contrary a replica set has already been initialized.\n\nIf the primary got killed and the volume i\n\n_Note: the README for this container is longer than the DockerHub length limit of 25000, so it has been trimmed. The full README can be found at https://techdocs.broadcom.com/us/en/vmware-tanzu/bitnami-secure-images/bitnami-secure-images/services/bsi-app-doc/apps-containers-mongodb-index.html_","has_starred","hub_user","immutable_tags_settings",{"_119":11,"_120":121},"enabled","rules",[122],".*","is_automated","permissions",{"_126":21,"_127":11,"_128":11},"read","write","admin","user","storage_size",1340610036108,"isOrg","reponame","tag","canDeleteTags","isHubSbxKitsEnabled","currentTab","","tagAttestations","displaySecurityMetadata","showSbxLogoOverride","routes/_layout.layers.$namespace.$reponame.$tag.(images).($imageUrlDigest)._index",{"_27":28,"_63":-7,"_61":-7,"_62":-7,"_29":144,"_35":36,"_146":-7,"_147":11},{"_31":32,"_33":34,"_35":36,"_37":38,"_39":40,"_41":145,"_43":44,"_45":34,"_46":47,"_48":49,"_50":51,"_52":53,"_54":-5,"_55":44,"_56":57,"_58":21},[],"imageWithLayers","hasPermissionToViewRepoSettings","actionData","errors"]

bitnami/mongodb:sha256-127db7f492afa5f6952f954d50da536a378784d689ac23d80b359811909596ae.metadata