Supported tags and respective
Where to file issues:
the Docker Community
Supported Docker versions:
the latest release (down to 1.6 on a best-effort basis)
What is MongoDB?
MongoDB (from "humongous") is a cross-platform document-oriented database. Classified as a NoSQL database, MongoDB eschews the traditional table-based relational database structure in favor of JSON-like documents with dynamic schemas (MongoDB calls the format BSON), making the integration of data in certain types of applications easier and faster. Released under a combination of the GNU Affero General Public License and the Apache License, MongoDB is free and open-source software.
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 Craigslist, eBay, Foursquare, SourceForge, Viacom, and the New York Times, among others. MongoDB is the most popular NoSQL database system.
How to use this image
mongo server instance
$ docker run --name some-mongo -d amd64/mongo:tag
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 container
The MongoDB server in the image listens on the standard MongoDB port,
27017, so connecting via container linking or Docker networks will be the be the same as connecting to a remote
mongod. The following example starts another MongoDB container instance and runs the
mongo 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 --link some-mongo:mongo --rm amd64/mongo mongo --host mongo test
some-mongo is the name of your original
docker stack deploy or
# Use root/example as user/password credentials version: '3.1' 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_ADMINUSERNAME: root ME_CONFIG_MONGODB_ADMINPASSWORD: example
docker stack deploy -c stack.yml mongo (or
docker-compose -f stack.yml up), wait for it to initialize completely, and visit
http://host-ip:8081 (as appropriate).
Container shell access and viewing MongoDB logs
docker exec command allows you to run commands inside a Docker container. The following command line will give you a bash shell inside your
$ docker exec -it some-mongo bash
The MongoDB Server log is available through Docker's container log:
$ docker logs some-mongo
See the MongoDB manual for information on using and configuring MongoDB for things like replica sets and sharding.
Customize configuration without configuration file
Most MongoDB configuration can be set through flags to
mongod. The entrypoint of the image is created to pass its arguments along to
mongod. See below an example of setting MongoDB to use a smaller default file size via
$ docker run --name some-mongo -d amd64/mongo --smallfiles
And here is the same with a
version: '3.1' services: mongo: image: amd64/mongo command: --smallfiles
To see the full list of possible options, check the MonogDB manual on
mongod or check the
--help output of
$ docker run -it --rm amd64/mongo --help
Using a custom MongoDB configuration file
For 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 amd64/mongo or mounting it from the host machine to the container. See the MongoDB manual for a full list of configuration file options.
/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 amd64/mongo --config /etc/mongo/mongod.conf
When 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 have 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.
These 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. Both 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 Initializing a fresh instance below). The following is an example of using these two variables to create a MongoDB instance and then using the
mongo cli to connect against the
admin authentication database.
$ docker run -d --name some-mongo -e MONGO_INITDB_ROOT_USERNAME=mongoadmin -e MONGO_INITDB_ROOT_PASSWORD=secret amd64/mongo $ docker run -it --rm --link some-mongo:mongo amd64/mongo mongo --host mongo -u mongoadmin -p secret --authenticationDatabase admin some-db > db.getName(); some-db
If you do not provide these two variables or do not set the
--auth flag with your own custom user setup, then MongoDB will not require authentication. For more details about the functionality described here, please see the sections in the official documentation which describe authentication and authorization in more detail.
This variable allows you to specify the name of a database to be used for creation scripts in
As 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/<secret_name> files. For example:
$ docker run --name some-mongo -e MONGO_INITDB_ROOT_PASSWORD_FILE=/run/secrets/mongo-root -d amd64/mongo
Currently, this is only supported for
Initializing a fresh instance
When a container is started for the first time it will execute files with extensions
.js that are found in
/docker-entrypoint-initdb.d. Files will be executed in alphabetical order.
.js files will be executed by
mongo using the database specified by the
MONGO_INITDB_DATABASE variable, if it is present, or
test otherwise. You may also switch databases within the
Where to Store Data
Important 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 available, 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): The default Docker setup on Windows and OS X uses a VirtualBox VM to host the Docker daemon. Unfortunately, the mechanism VirtualBox uses to share folders between the host system and the Docker container is not compatible with the memory mapped files used by MongoDB (see vbox bug, docs.mongodb.org and related jira.mongodb.org bug). This means that it is not possible to run a MongoDB container with the data directory mapped to the host.
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.
mongocontainer like this:
$ docker run --name some-mongo -v /my/own/datadir:/data/db -d amd64/mongo
-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 (see docs.mongodb.com for more details).
Note that users on host systems with SELinux enabled may see issues with this. The current workaround is to assign the relevant SELinux policy type to the new data directory so that the container will be allowed to access it:
$ chcon -Rt svirt_sandbox_file_t /my/own/datadir
Creating database dumps
Most of the normal tools will work, although their usage might be a little convoluted in some cases to ensure they have 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 <database_name> --archive' > /some/path/on/your/host/all-collections.archive
View license information for the software contained in this image.
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
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.