tree 4c0dbe41085896e2839953f027b6c9d9157f2713
parent efe8a830f9a44a5c6baacf382c6269703bdc7bbd
author Will Holley <willholley@apache.org> 1594321719 +0100
committer GitHub <noreply@github.com> 1594321719 -0400
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJfB2s3CRBK7hj4Ov3rIwAAdHIIAFTMfC2vbsWO9iDWYkZUS8sM
 2GUZKUU2nShd39QVZC+KJQriJgHQfXBJNOGYMdzjLh2KcpW4pj+kMlGra6tZXYRz
 OfjTtsnIzeVD+qUQtdwqLTYwQ1nZvoAiZvbVDzYj54lLPZtQ7P5N+cgHX7mad7pG
 LDonfrlhg4zfWUnzo/RdQqWeBiDlVYfECJHdabKdk+LuUBLVCmMUoIAh2GNOMLJ9
 4KQxfnIGmShtetDD5XMoZ07Q/qjuGRRbPcJ96yYCdcu9AOIT7/OAlIpCccfil6ec
 bOSoHyBOrNBY4uXnh2Io7qaNiPO4WnVwbfFaBcPupkpaMuUUo7U//l+CG1TpC18=
 =vUBf
 -----END PGP SIGNATURE-----
 

Combined CouchDB / Clouseau dockerfile (#187)

This adds a Dockerfile which contains both CouchDB and Clouseau
in a single container. This is useful because in most containerized
environments, EPMD runs in the CouchDB container; restarting the
CouchDB container can therefore lead to Clouseau becoming orphaned
because EPMD is also killed.

The container is based on the Red Hat UBI and uses runit to supervise
both CouchDB and Clouseau. UBI is used mostly for familiarity (this
is how we build a combined container at IBM), but it serves as a
reference for anybody looking to port to other base images.

The dockerfile entrypoint is modified to configure CouchDB and Clouseau
in an Erlang cluster. It's equally possible to run the container in
e.g. Kubernetes or Docker Compose without the dockerfile entrypoint;
the user would then need to write out the configuration files via their
configuration management system and call `/sbin/runsvdir-start` directly.

Both CouchDB and Clouseau will, by default, run under the UID 5984
(CouchDB) and GID 0. If the container is started as a non-root user,
that ambient UID/GID is used instead.

Refs #8