manios/mongo Docker 镜像 - 轩辕镜像 | Docker 镜像高效稳定拉取服务

Based on commit 7b2fe2c of official Mongo image version 3.0.15.

Supported tags and respective Dockerfile links

• 2.6.0, 2.6, latest (2.6.0/Dockerfile)

![]([] ![build status badge]([]

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.

***.org/wiki/MongoDB

!logo

How to use this image

start a mongo instance

console
$ docker run --name some-mongo -d manios/mongo

This image includes EXPOSE 27017 (the mongo port), so standard container linking will make it automatically available to the linked containers (as the following examples illustrate).

connect to it from an application

console
$ docker run --name some-app --link some-mongo:manios/mongo -d application-that-uses-mongo

... or via mongo

console
$ docker run -it --link some-mongo:mongo --rm manios/mongo sh -c 'exec mongo "$MONGO_PORT_27017_TCP_ADDR:$MONGO_PORT_27017_TCP_PORT/test"'

Configuration

See the official docs for infomation on using and configuring MongoDB for things like replica sets and sharding.

Just add the --storageEngine argument if you want to use the WiredTiger storage engine in MongoDB 3.0 and above without making a config file. WiredTiger is the default storage engine in MongoDB 3.2 and above. Be sure to check the docs on how to upgrade from older versions.

console
$ docker run --name some-mongo -d manios/mongo --storageEngine wiredTiger

Authentication and Authorization

MongoDB does not require authentication by default, but it can be configured to do so. For more details about the functionality described here, please see the sections in the official documentation which describe authentication and authorization in more detail.

Start the Database

console
$ docker run --name some-mongo -d manios/mongo --auth

Add the Initial Admin User

console
$ docker exec -it some-mongo mongo admin
connecting to: admin
> db.createUser({ user: 'jsmith', pwd: 'some-initial-password', roles: [ { role: "userAdminAnyDatabase", db: "admin" } ] });
Successfully added user: {
	"user" : "jsmith",
	"roles" : [
		{
			"role" : "userAdminAnyDatabase",
			"db" : "admin"
		}
	]
}

Connect Externally

console
$ docker run -it --rm --link some-mongo:mongo manios/mongo mongo -u jsmith -p some-initial-password --authenticationDatabase admin some-mongo/some-db
> db.getName();
some-db

Write to log file in a volume

Traditionally this image does output the logs to stdout. In order to write logs to a file use the following:

console
$ docker run \
   -d \
   --name some-mongo \
   -v /my/own/logdir:/data/log \
   manios/mongo:2.6 
     --logpath /data/log/mongo.log \

The -v /my/own/logdir:/var/log/mongodb part of the command mounts the /my/own/logdir directory from the underlying host system as /var/log/mongodb inside the container, where MongoDB by default will write its log files.

Share the same datetime with host

By default docker has UTC as its timezone. If you want to have the same datetime as the host inside the container and show it properly in logs you can use the following:

console
$ docker run \
   -d \
   --name some-mongo \
   -v /my/own/logdir:/data/log \
   -v /etc/localtime:/etc/localtime \
   manios/mongo:2.6 
     --logpath /data/log/mongo.log \

The -v /etc/localtime:/etc/localtime part of the command mounts the /etc/localtime file from the underlying host system as :/etc/localtime inside the container. Thus MongoDB will display the date and time using the same timezone as the host in its log files.

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:

1. Create a data directory on a suitable volume on your host system, e.g. /my/own/datadir.

2. Start your mongo container like this:

   console
   $ docker run --name some-mongo -v /my/own/datadir:/data/db -d manios/mongo:tag
   

The -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:

console
$ chcon -Rt svirt_sandbox_file_t /my/own/datadir

mongo:<version>

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.