Dockerized MongoDB Replica Set
This MongoDB Docker container is intended to be used to set up a 3 node replica set.
Mongo version: 3.4.0
A MongoDB replica set consists of at least 3 Mongo instances. In this case, they will be a primary, two secondary, and optional an arbiter. To use this project as a replica set, you simply launch three instances of this container across three separate host servers and the primary will configure your users and replica set. Also note that each server must be able to access the others (discovery must work in both directions).
You will need to create your own custom build of this image to generate a unique keyfile that Mongo uses for internal authentication between replica set members. Each of your replica set members needs to have the same key, so be sure to use the same image in each location. Once using your build in production do NOT publish your Docker image to a public repo because it will container your private key.
docker build -t diceone/mongo-rep:latest .
docker-compose example without Volumes for local testing
version: '2' services: mongo1: restart: always environment: MONGO_ROLE: primary MONGO_ROOT_USER: root MONGO_ROOT_PASSWORD: root MONGO_APP_USER: node MONGO_APP_PASSWORD: node MONGO_APP_DATABASE: node MONGO_REP_SET: TEST tty: true ports: - 27027:27017/tcp hostname: mongo1 image: diceone/mongo-rep:latest stdin_open: true mongo2: restart: always environment: MONGO_REP_SET: TEST tty: true hostname: mongo2 image: diceone/mongo-rep:latest stdin_open: true ports: - 27028:27017/tcp mongo3: restart: always environment: MONGO_REP_SET: TEST tty: true hostname: mongo3 image: diceone/mongo-rep:latest stdin_open: true ports: - 27029:27017/tcp
docker run -d -p 27017:27017 diceone/mongo-rep:latest
Arbiter (optional) if needed (at the moment outlined)
The only difference here is you can turn off journaling. From the official docs:
An arbiter does not store data, but until the arbiter’s mongod process is added to the replica set, the arbiter will act like any other mongod process and start up with a set of data files and with a full-sized journal. To minimize the default creation of data, you can disable journaling.
docker run -d -p 27017:27017 -e JOURNLING=false diceone/mongo-rep:latest
The primary is responsible for setting up users and configuring the replica set, so this is where all of the configuration happens. Once your secondary and arbiter are up and running, launch your primary with:
docker run -d -p 27017:27017 \ -e MONGO_ROLE="primary" \ -e MONGO_SECONDARY="hostname or IP of secondary" \ -e MONGO_ARBITER="hostname or IP of arbiter" \ -e MONGO_ROOT_USER="myRootUser" \ -e MONGO_ROOT_PASSWORD="myRootUserPassword" \ -e MONGO_APP_USER="myAppUser" \ -e MONGO_APP_PASSWORD="myAppUserPassword" \ -e MONGO_APP_DATABASE="myAppDatabase" \ diceone/mongo-rep:latest
The primary will start up, configure your root and app users, shut down, and then start up once more and configure the replica set. Assuming the secondary and arbiter are reachable, the server will now be ready for authenticated connections. You can use the standard two server Mongo URL to connect to the primary/secondaries like this:
Note that the following connection url is using default env var values (more info on those below), so it should work if you haven't overwritten any of the variables yourself.
Here are all of the available environment variables and their defaults. Note that if you set
MONGO_REP_SET, you must set it to the same value on all 3 containers.
# mongod config MONGO_STORAGE_ENGINE wiredTiger MONGO_JOURNALING true MONGO_REP_SET rs0 MONGO_AUTH true MONGO_OPLOG_SIZE # not set, but you can override the default MONGO_SECONDARY mongo2:27017 MONGO_THIRD mongo3:27017 #MONGO_ARBITER mongo3:27017 MONGO_DB_PATH /data/db # mongo root user MONGO_ROOT_USER root MONGO_ROOT_PASSWORD root123 # mongo app user + database (user is given oplog access) MONGO_APP_USER myAppUser MONGO_APP_PASSWORD myAppPassword MONGO_APP_DATABASE myAppDatabase