commit	e5e33bb6cac5302927bb83d1c23d845ff6adc094	[log] [tgz]
author	klaemo <klaemo@fastmail.fm>	Fri Aug 21 20:31:00 2015 +0200
committer	klaemo <klaemo@fastmail.fm>	Fri Aug 21 20:31:44 2015 +0200
tree	ccbb065936c34d3a751ac8d73e3cf78e9f1b236f
parent	2699a91965230a8b1d77f2c960faf282ba179319 [diff]

tree: ccbb065936c34d3a751ac8d73e3cf78e9f1b236f

README.md

YADC

Yet Another Dockerized CouchDB. Put the couch in a docker container and ship it anywhere.

If you're looking for a CouchDB with SSL support you can check out klaemo/couchdb-ssl

Version (stable): CouchDB 1.6.1, Erlang 17.5.3
Version (dev): CouchDB 2.0 developer preview, Erlang 18.0

Run (stable)

Available in the docker index as klaemo/couchdb

[sudo] docker pull klaemo/couchdb:latest

# expose it to the world on port 5984
[sudo] docker run -d -p 5984:5984 --name couchdb klaemo/couchdb

curl http://localhost:5984

Run (stable with mounted Volume)

[sudo] docker pull klaemo/couchdb:latest

# expose it to the world on port 5984 and use your current directory as the CouchDB Database directory
[sudo] docker run -d -p 5984:5984 -v $(pwd):/usr/local/var/lib/couchdb --name couchdb klaemo/couchdb

curl http://localhost:5984

Features

built on top of the solid and small debian:wheezy base image
exposes CouchDB on port 5984 of the container
runs everything as user couchdb (security ftw!)
docker volumes for data and logs

The previous version of this image used to come with a process manager to keep CouchDB running. As of Docker 1.2 you can use the --restart flag to accomplish this.

Run (dev)

Available on the docker registry as klaemo/couchdb:2.0-dev

# expose the cluster to the world
[sudo] docker run -p 5984:5984 klaemo/couchdb:2.0-dev

[ * ] Setup environment ... ok
[ * ] Ensure CouchDB is built ... ok
[ * ] Prepare configuration files ... ok
[ * ] Start node node1 ... ok
[ * ] Start node node2 ... ok
[ * ] Start node node3 ... ok
[ * ] Check node at http://127.0.0.1:15984/ ... failed: [Errno socket error] [Errno 111] Connection refused
[ * ] Check node at http://127.0.0.1:25984/ ... ok
[ * ] Check node at http://127.0.0.1:35984/ ... ok
[ * ] Check node at http://127.0.0.1:15984/ ... ok
[ * ] Running cluster setup ... ok
[ * ] Developers cluster is set up at http://127.0.0.1:15984.
Admin username: root
Password: 37l7YDQJ
Time to hack! ...

...or you can pass arguments to the binary

docker run -i -t klaemo/couchdb:2.0-dev --admin=foo:bar

Note: The cluster will be exposed on port 5984, because it internally uses haproxy.

Build your own

You can use klaemo/couchdb as the base image for your own couchdb instance. You might want to provide your own version of the following files:

local.ini for CouchDB

Example Dockerfile:

FROM klaemo/couchdb

COPY local.ini /usr/local/etc/couchdb/

and then build and run

[sudo] docker build -t you/awesome-couchdb .
[sudo] docker run -d -p 5984:5984 -v ~/couchdb:/usr/local/var/lib/couchdb you/awesome-couchdb

Contributing

Please use Github issues for any questions, bugs, feature requests. :)

Contributors

@joeybaker