Dockerfile to create a Docker container image for MongoDB.
MongoDB 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, making the integration of data in certain types of applications easier and faster
If you find this image useful here's how you can help:
Before reporting your issue please try updating Docker to the latest version and check if it resolves the issue. Refer to the Docker installation guide for instructions.
SELinux users should try disabling SELinux using the command setenforce 0 to see if it resolves the issue.
If the above recommendations do not help then report your issue along with the following information:
docker version and docker info commandsdocker run command or docker-compose.yml used to start the image. Mask out the sensitive bits.Automated builds of the image are available on Dockerhub and is the recommended method of installation.
Note: Builds are also available on Quay.io
docker pull sameersbn/mongodb:latest
Alternatively you can build the image yourself.
docker build -t sameersbn/mongodb github.com/sameersbn/docker-mongodb
Start MongoDB using:
docker run --name mongodb -d --restart=always \
--publish 27017:27017 \
--volume /srv/docker/mongodb:/var/lib/mongodb \
sameersbn/mongodb:latest
Alternatively, you can use the sample docker-compose.yml file to start the container using Docker Compose
You can customize the launch command of the MongoDB server by specifying arguments to mongod on the docker run command. For example the following command prints the help menu of mongod command:
docker run --name mongodb -it --rm \
--publish 27017:27017 \
--volume /srv/docker/mongodb:/var/lib/mongodb \
sameersbn/mongodb:latest --help
For MongoDB to preserve its state across container shutdown and startup you should mount a volume at /var/lib/mongodb.
The Quickstart command already mounts a volume for persistence.
SELinux users should update the security context of the host mountpoint so that it plays nicely with Docker:
mkdir -p /srv/docker/mongodb
chcon -Rt svirt_sandbox_file_t /srv/docker/mongodb
To access the MongoDB logs, located at /var/log/mongodb, you can use docker exec. For example, if you want to tail the logs:
docker exec -it mongodb tail -f /var/log/mongodb/mongod.log
Per default the container is configured to run mongdob as user and group mongodb with uid 102 and gid 65534. The host possibly uses this ids for different purposes leading to unfavorable effects. From the host it appears as if the mounted data volumes are owned by the host's user 102 and group 65534`.
Also the container processes seem to be executed as this host's user/group. The container can be configured to map the uid and gid of mongodb to different ids on host by passing the environment variables USERMAP_UID and USERMAP_GID. The following command maps the ids to user and group mongodb on the host.
docker run --name mongodb -it --rm [options] \
--env "USERMAP_UID=$(id -u mongodb)" --env "USERMAP_GID=$(id -g mongodb)" \
sameersbn/mongodb:latest
To upgrade to newer releases:
docker pull sameersbn/mongodb:latest
docker stop mongodb
docker rm -v mongodb
docker run -name mongodb -d \
[OPTIONS] \
sameersbn/mongodb:latest
For debugging and maintenance purposes you may want access the containers shell. If you are using Docker version 1.3.0 or higher you can access a running containers shell by starting bash using docker exec:
docker exec -it mongodb bash
Content type
Image
Digest
sha256:2ee22354c…
Size
78.8 MB
Last updated
over 10 years ago
docker pull sameersbn/mongodb