commit | 7d9e17443cb8f6427c38ce2b86b199ddc9f2b5b9 | [log] [tgz] |
---|---|---|
author | cristian <criscalovis@gmail.com> | Wed Jan 28 22:43:51 2015 +0100 |
committer | klaemo <klaemo@fastmail.fm> | Wed Jan 28 22:45:05 2015 +0100 |
tree | 4b741469181f415b92e5ec9a4a272a78c7b0eaab | |
parent | 9e039c63fd62e6398bd2e07ec67f870cec255be6 [diff] |
dev: wait for an additional 1s in dev/run command - workaround for #16
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
CouchDB 1.6.1
CouchDB 2.0 developer preview
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
debian:wheezy
base image5984
of the containercouchdb
(security ftw!)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.
Available on the docker registry as klaemo/couchdb:2.0-dev
# expose the cluster to the world [sudo] docker run -i -t -p 15984:15984 -p 25984:25984 -p 35984:35984 --name couchdb klaemo/couchdb:2.0-dev curl http://localhost:15984 curl http://localhost:25984 curl http://localhost:35984
...or you can pass arguments to the binary
docker run -i -t klaemo/couchdb:2.0-dev --admin=foo:bar
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 CouchDBExample 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
Please use Github issues for any questions, bugs, feature requests. :)