Sign inSign up

redgeoff/couchdb

By redgeoff

•Updated almost 9 years ago

CouchDB in a docker container

Image
0

3.3K

redgeoff/couchdb repository overview

⁠redgeoff-couchdb-docker

CouchDB in a docker container

⁠Example

docker run -d --name couchdb \
  -p 5984:5984 \
  -v /home/ubuntu/common:/home/couchdb/common \
  -e COUCHDB_DATA_DIR="/home/couchdb/common/data/couchdb1.mydomain.com" \
  -e COUCHDB_USER='admin' \
  -e COUCHDB_HASHED_PASSWORD='-pbkdf2-b1eb7a68b0778a529c68d30749954e9e430417fb,4da0f8f1d98ce649a9c5a3845241ae24,10' \
  -e COUCHDB_COOKIE='mycookie' \
  -e COUCHDB_SECRET='mysecret' \
  redgeoff/couchdb

⁠Example with SSL

We assume /home/ubuntu/common/ssl/mydomain.com.crt and /home/ubuntu/common/ssl/mydomain.com.key are the certificate and private key for your SSL config.

docker run -d --name couchdb \
  -p 6984:6984 \
  -v /home/ubuntu/common:/home/couchdb/common \
  -e COUCHDB_DATA_DIR="/home/couchdb/common/data/couchdb1.mydomain.com" \
  -e COUCHDB_USER='admin' \
  -e COUCHDB_HASHED_PASSWORD='-pbkdf2-b1eb7a68b0778a529c68d30749954e9e430417fb,4da0f8f1d98ce649a9c5a3845241ae24,10' \
  -e COUCHDB_COOKIE='mycookie' \
  -e COUCHDB_SECRET='mysecret' \
  -e COUCHDB_CERT_FILE="/home/couchdb/common/ssl/mydomain.com.crt" \
  -e COUCHDB_KEY_FILE="/home/couchdb/common/ssl/mydomain.com.key" \
  -e COUCHDB_CACERT_FILE="/home/couchdb/common/ssl/mydomain.com.crt" \
  redgeoff/couchdb

⁠Example with SSL and custom local.ini

We assume /home/ubuntu/common/etc/local.ini contains any custom config, e.g.

[chttpd]
bind_address = any

[httpd]
bind_address = any

[couchdb]
max_dbs_open=1000

Then run:

docker run -d --name couchdb \
  -p 6984:6984 \
  -v /home/ubuntu/common:/home/couchdb/common \
  -v /home/ubuntu/common/etc/local.ini:/home/couchdb/couchdb/etc/local.d/local.ini \
  -e COUCHDB_DATA_DIR="/home/couchdb/common/data/couchdb1.mydomain.com" \
  -e COUCHDB_USER='admin' \
  -e COUCHDB_HASHED_PASSWORD='-pbkdf2-b1eb7a68b0778a529c68d30749954e9e430417fb,4da0f8f1d98ce649a9c5a3845241ae24,10' \
  -e COUCHDB_COOKIE='mycookie' \
  -e COUCHDB_SECRET='mysecret' \
  -e COUCHDB_CERT_FILE="/home/couchdb/common/ssl/mydomain.com.crt" \
  -e COUCHDB_KEY_FILE="/home/couchdb/common/ssl/mydomain.com.key" \
  -e COUCHDB_CACERT_FILE="/home/couchdb/common/ssl/mydomain.com.crt" \
  redgeoff/couchdb

⁠Create Cluster

For example, assume that you have the following DNS config:

192.168.50.10 couchdb1.mydomain.com
192.168.50.11 couchdb2.mydomain.com

On server 1, run:

docker run -d --name couchdb \
  -p 5984:5984 \
  -p 6984:6984 \
  -p 5986:5986 \
  -p 4369:4369 \
  -p 9100-9200:9100-9200 \
  -v /home/ubuntu/common:/home/couchdb/common \
  -v /home/ubuntu/common/etc/local.ini:/home/couchdb/couchdb/etc/local.d/local.ini \
  -e COUCHDB_DATA_DIR="/home/couchdb/common/data/couchdb1.mydomain.com" \
  -e COUCHDB_USER='admin' \
  -e COUCHDB_HASHED_PASSWORD='-pbkdf2-b1eb7a68b0778a529c68d30749954e9e430417fb,4da0f8f1d98ce649a9c5a3845241ae24,10' \
  -e COUCHDB_COOKIE='mycookie' \
  -e COUCHDB_NODE_NAME='192.168.50.10' \
  -e COUCHDB_SECRET='mysecret' \
  -e COUCHDB_CERT_FILE="/home/couchdb/common/ssl/mydomain.com.crt" \
  -e COUCHDB_KEY_FILE="/home/couchdb/common/ssl/mydomain.com.key" \
  -e COUCHDB_CACERT_FILE="/home/couchdb/common/ssl/mydomain.com.crt" \
  redgeoff/couchdb

On server 2, run:

docker run -d --name couchdb \
  -p 5984:5984 \
  -p 6984:6984 \
  -p 5986:5986 \
  -p 4369:4369 \
  -p 9100-9200:9100-9200 \
  -v /home/ubuntu/common:/home/couchdb/common \
  -v /home/ubuntu/common/etc/local.ini:/home/couchdb/couchdb/etc/local.d/local.ini \
  -e COUCHDB_DATA_DIR="/home/couchdb/common/data/couchdb2.mydomain.com" \
  -e COUCHDB_USER='admin' \
  -e COUCHDB_HASHED_PASSWORD='-pbkdf2-b1eb7a68b0778a529c68d30749954e9e430417fb,4da0f8f1d98ce649a9c5a3845241ae24,10' \
  -e COUCHDB_COOKIE='mycookie' \
  -e COUCHDB_NODE_NAME='192.168.50.11' \
  -e COUCHDB_SECRET='mysecret' \
  -e COUCHDB_CERT_FILE="/home/couchdb/common/ssl/mydomain.com.crt" \
  -e COUCHDB_KEY_FILE="/home/couchdb/common/ssl/mydomain.com.key" \
  -e COUCHDB_CACERT_FILE="/home/couchdb/common/ssl/mydomain.com.crt" \
  redgeoff/couchdb

Create cluster:

./create-cluster.sh admin admin 5984 5986 "192.168.50.12 192.168.50.11"

You can then use a load balancer to balance port 6984 traffic over 192.168.50.12 and 192.168.50.11. You can also do the the SSL termination directly on the load balancer and have the load balancer connect with the CouchDB nodes on port 5984. For better security, you should use a firewall to make sure to only allow outside traffic via the load balancer.

⁠Upgrade to latest image

$ docker pull redgeoff/couchdb
$ docker rm couchdb --force
$ docker run -d --name couchdb ...

⁠On AWS

See Running a CouchDB 2.0 Cluster in Production on AWS with Docker⁠

Tag summary

Content type

Image

Digest

Size

206.3 MB

Last updated

almost 9 years ago

docker pull redgeoff/couchdb