Maintained by: the Docker Community
Where to get help: the Docker Community Slack, Server Fault, Unix & Linux, or Stack Overflow
Supported tags and respective Dockerfile links(See "What's the difference between 'Shared' and 'Simple' tags?" in the FAQ.)
Simple Tags8.2.3-noble, 8.2-noble, 8-noble, noble
8.2.3-windowsservercore-ltsc2025, 8.2-windowsservercore-ltsc2025, 8-windowsservercore-ltsc2025, windowsservercore-ltsc2025
8.2.3-windowsservercore-ltsc2022, 8.2-windowsservercore-ltsc2022, 8-windowsservercore-ltsc2022, windowsservercore-ltsc2022
8.2.3-nanoserver-ltsc2022, 8.2-nanoserver-ltsc2022, 8-nanoserver-ltsc2022, nanoserver-ltsc2022
8.0.17-noble, 8.0-noble
8.0.17-windowsservercore-ltsc2025, 8.0-windowsservercore-ltsc2025
8.0.17-windowsservercore-ltsc2022, 8.0-windowsservercore-ltsc2022
8.0.17-nanoserver-ltsc2022, 8.0-nanoserver-ltsc2022
7.0.28-jammy, 7.0-jammy, 7-jammy
7.0.28-windowsservercore-ltsc2025, 7.0-windowsservercore-ltsc2025, 7-windowsservercore-ltsc2025
7.0.28-windowsservercore-ltsc2022, 7.0-windowsservercore-ltsc2022, 7-windowsservercore-ltsc2022
7.0.28-nanoserver-ltsc2022, 7.0-nanoserver-ltsc2022, 7-nanoserver-ltsc2022
Shared Tags8.2.3, 8.2, 8, latest:
8.2.3-noble 8.2.3-windowsservercore-ltsc2025 8.2.3-windowsservercore-ltsc20228.2.3-windowsservercore, 8.2-windowsservercore, 8-windowsservercore, windowsservercore:
8.2.3-windowsservercore-ltsc2025 8.2.3-windowsservercore-ltsc20228.2.3-nanoserver, 8.2-nanoserver, 8-nanoserver, nanoserver:
8.2.3-nanoserver-ltsc20228.0.17, 8.0:
8.0.17-noble 8.0.17-windowsservercore-ltsc2025 8.0.17-windowsservercore-ltsc20228.0.17-windowsservercore, 8.0-windowsservercore:
8.0.17-windowsservercore-ltsc2025 8.0.17-windowsservercore-ltsc20228.0.17-nanoserver, 8.0-nanoserver:
8.0.17-nanoserver-ltsc20227.0.28, 7.0, 7:
7.0.28-jammy 7.0.28-windowsservercore-ltsc2025 7.0.28-windowsservercore-ltsc20227.0.28-windowsservercore, 7.0-windowsservercore, 7-windowsservercore:
7.0.28-windowsservercore-ltsc2025 7.0.28-windowsservercore-ltsc20227.0.28-nanoserver, 7.0-nanoserver, 7-nanoserver:
7.0.28-nanoserver-ltsc2022 Quick reference (cont.)Where to file issues: https://github.com/docker-library/mongo/issues
Supported architectures: (more info) amd64, arm64v8, windows-amd64
Published image artifact details: repo-info repo's repos/mongo/ directory (history) (image metadata, transfer size, etc)
Image updates: official-images repo's library/mongo label official-images repo's library/mongo file (history)
Source of this description: docs repo's mongo/ directory (history)
What is MongoDB?MongoDB is a free and open-source cross-platform document-oriented database program. Classified as a NoSQL database program, MongoDB uses JSON-like documents with schemata. MongoDB is developed by MongoDB Inc., and is published under a combination of the Server Side Public License and the Apache License.
First developed by the software company 10gen (now MongoDB Inc.) in October 2007 as a component of a planned platform as a service product, the company shifted to an open source development model in 2009, with 10gen offering commercial support and other services. Since then, MongoDB has been adopted as backend software by a number of major websites and services, including MetLife, Barclays, ADP, UPS, Viacom, and the New York Times, among others. MongoDB is the most popular NoSQL database system.
wikipedia.org/wiki/MongoDB
SecurityBy default Mongo's configuration requires no authentication for access, even for the administrative user. It is highly recommended to set a root user name and password if you plan on exposing your Mongo instance to the internet. See the "MONGO_INITDB_ROOT_USERNAME, MONGO_INITDB_ROOT_PASSWORD" section below for instructions and the MongoDB Security documentation for a more complete treatment.
How to use this image Start a mongo server instance $ docker run --name some-mongo -d mongo:tag... where some-mongo is the name you want to assign to your container and tag is the tag specifying the MongoDB version you want. See the list above for relevant tags.
Connect to MongoDB from another Docker containerThe MongoDB server in the image listens on the standard MongoDB port, 27017, so connecting via Docker networks will be the same as connecting to a remote mongod. The following example starts another MongoDB container instance and runs the mongosh (use mongo with 4.x versions) command line client against the original MongoDB container from the example above, allowing you to execute MongoDB statements against your database instance:
$ docker run -it --network some-network --rm mongo mongosh --host some-mongo test... where some-mongo is the name of your original mongo container.
... via docker composeExample compose.yaml for mongo:
services: mongo: image: mongo restart: always environment: MONGO_INITDB_ROOT_USERNAME: root MONGO_INITDB_ROOT_PASSWORD: example mongo-express: image: mongo-express restart: always ports: - 8081:8081 environment: ME_CONFIG_MONGODB_URL: mongodb://root:example@mongo:27017/ ME_CONFIG_BASICAUTH_ENABLED: true ME_CONFIG_BASICAUTH_USERNAME: mongoexpressuser ME_CONFIG_BASICAUTH_PASSWORD: mongoexpresspassRun docker compose up, wait for it to initialize completely, and visit http://localhost:8081 or http://host-ip:8081 (as appropriate).
Container shell access and viewing MongoDB logsThe docker exec command allows you to run commands inside a Docker container. The following command line will give you a bash shell inside your mongo container:
$ docker exec -it some-mongo bashThe MongoDB Server log is ailable through Docker's container log:
$ docker logs some-mongo ConfigurationSee the MongoDB manual for information on using and configuring MongoDB for things like replica sets and sharding.
Customize configuration without configuration fileMost MongoDB configuration options can be set through flags to mongod. The entrypoint of the image passes its arguments along to mongod. Example below enables MongoDB query profiler via docker run.
$ docker run --name some-mongo -d mongo --profile 1The same can be achieved with a compose.yaml file
services: mongo: image: mongo command: --profile 1To see the full list of possible options, check the MongoDB manual on mongod or check the --help output of mongod:
$ docker run -it --rm mongo --help Using a custom MongoDB configuration fileFor a more complicated configuration setup, you can still use the MongoDB configuration file. mongod does not read a configuration file by default, so the --config option with the path to the configuration file needs to be specified. Create a custom configuration file and put it in the container by either creating a custom Dockerfile FROM mongo or mounting it from the host machine to the container. See the MongoDB manual for a full list of configuration file options.
For example, /my/custom/mongod.conf is the path to the custom configuration file. Then start the MongoDB container like the following:
$ docker run --name some-mongo -v /my/custom:/etc/mongo -d mongo --config /etc/mongo/mongod.conf Environment VariablesWhen you start the mongo image, you can adjust the initialization of the MongoDB instance by passing one or more environment variables on the docker run command line. Do note that none of the variables below will he any effect if you start the container with a data directory that already contains a database: any pre-existing database will always be left untouched on container startup.
MONGO_INITDB_ROOT_USERNAME, MONGO_INITDB_ROOT_PASSWORDThese variables, used in conjunction, create a new user and set that user's password. This user is created in the admin authentication database and given the role of root, which is a "superuser" role.
The following is an example of using these two variables to create a MongoDB instance and then using the mongosh cli (use mongo with 4.x versions) to connect against the admin authentication database.
$ docker run -d --network some-network --name some-mongo \ -e MONGO_INITDB_ROOT_USERNAME=mongoadmin \ -e MONGO_INITDB_ROOT_PASSWORD=secret \ mongo $ docker run -it --rm --network some-network mongo \ mongosh --host some-mongo \ -u mongoadmin \ -p secret \ --authenticationDatabase admin \ some-db > db.getName(); some-dbBoth variables are required for a user to be created. If both are present then MongoDB will start with authentication enabled (mongod --auth).
Authentication in MongoDB is fairly complex, so more complex user setup is explicitly left to the user via /docker-entrypoint-initdb.d/ (see the Initializing a fresh instance and Authentication sections below for more details).
MONGO_INITDB_DATABASEThis variable allows you to specify the name of a database to be used for creation scripts in /docker-entrypoint-initdb.d/*.js (see Initializing a fresh instance below). MongoDB is fundamentally designed for "create on first use", so if you do not insert data with your JaScript files, then no database is created.
Docker SecretsAs an alternative to passing sensitive information via environment variables, _FILE may be appended to the previously listed environment variables, causing the initialization script to load the values for those variables from files present in the container. In particular, this can be used to load passwords from Docker secrets stored in /run/secrets/ files. For example:
$ docker run --name some-mongo -e MONGO_INITDB_ROOT_PASSWORD_FILE=/run/secrets/mongo-root -d mongoCurrently, this is only supported for MONGO_INITDB_ROOT_USERNAME and MONGO_INITDB_ROOT_PASSWORD.
Initializing a fresh instanceWhen a container is started for the first time it will execute files with extensions .sh and .js that are found in /docker-entrypoint-initdb.d. Files will be executed in alphabetical order. .js files will be executed by mongosh (mongo on versions below 6) using the database specified by the MONGO_INITDB_DATABASE variable, if it is present, or test otherwise. You may also switch databases within the .js script.
AuthenticationAs noted above, authentication in MongoDB is fairly complex (although disabled by default). For details about how MongoDB handles authentication, please see the relevant upstream documentation:
mongod --auth Security > Authentication Security > Role-Based Access Control Security > Role-Based Access Control > Built-In Roles Security > Enable Auth (tutorial)In addition to the /docker-entrypoint-initdb.d behior documented above (which is a simple way to configure users for authentication for less complicated deployments), this image also supports MONGO_INITDB_ROOT_USERNAME and MONGO_INITDB_ROOT_PASSWORD for creating a simple user with the role root in the admin authentication database, as described in the Environment Variables section above.
Ceats Where to Store DataImportant note: There are several ways to store data used by applications that run in Docker containers. We encourage users of the mongo images to familiarize themselves with the options ailable, including:
Let Docker manage the storage of your database data by writing the database files to disk on the host system using its own internal volume management. This is the default and is easy and fairly transparent to the user. The downside is that the files may be hard to locate for tools and applications that run directly on the host system, i.e. outside containers. Create a data directory on the host system (outside the container) and mount this to a directory visible from inside the container. This places the database files in a known location on the host system, and makes it easy for tools and applications on the host system to access the files. The downside is that the user needs to make sure that the directory exists, and that e.g. directory permissions and other security mechanisms on the host system are set up correctly.WARNING (Windows & OS X): When running the Linux-based MongoDB images on Windows and OS X, the file systems used to share between the host system and the Docker container is not compatible with the memory mapped files used by MongoDB (see documenation note and related bug). This means that it is not possible to run a MongoDB container with the data directory mapped to the host. To persist data between container restarts, we recommend using a local named volume instead (see docker volume create). Alternatively you can use the Windows-based images on Windows.
The Docker documentation is a good starting point for understanding the different storage options and variations, and there are multiple blogs and forum postings that discuss and give advice in this area. We will simply show the basic procedure here for the latter option above:
Create a data directory on a suitable volume on your host system, e.g. /my/own/datadir.
Start your mongo container like this:
$ docker run --name some-mongo -v /my/own/datadir:/data/db -d mongoThe -v /my/own/datadir:/data/db part of the command mounts the /my/own/datadir directory from the underlying host system as /data/db inside the container, where MongoDB by default will write its data files.
This image also defines a volume for /data/configdb for use with --configsvr.
Creating database dumpsMost of the normal tools will work, although their usage might be a little convoluted in some cases to ensure they he access to the mongod server. A simple way to ensure this is to use docker exec and run the tool from the same container, similar to the following:
$ docker exec some-mongo sh -c 'exec mongodump -d --archive' > /some/path/on/your/host/all-collections.archive Image VariantsThe mongo images come in many flors, each designed for a specific use case.
mongo:This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
Some of these tags may he names like jammy or noble in them. These are the suite code names for releases of Ubuntu and indicate which release the image is based on. If your image needs to install any additional packages beyond what comes with the image, you'll likely want to specify one of these explicitly to minimize breakage when there are new releases of Ubuntu.
mongo:-windowsservercoreThis image is based on Windows Server Core (mcr.microsoft.com/windows/servercore). As such, it only works in places which that image does, such as Windows 10 Professional/Enterprise (Anniversary Edition) or Windows Server 2016.
For information about how to get Docker running on Windows, please see the relevant "Quick Start" guide provided by Microsoft:
Windows Containers Quick Start LicenseView license information for the software contained in this image.
It is relevant to note the change from AGPL to SSPLv1 for all versions after October 16, 2018.
As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).
Some additional license information which was able to be auto-detected might be found in the repo-info repository's mongo/ directory.
As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.