Last changed
Be the first to hear about exciting product updates, critical vulnerability alerts, compare alternative images, and more.
Sign UpApache CouchDB is an open-source, document-oriented NoSQL database implemented in Erlang.
Chainguard Images are regularly-updated, minimal container images with low-to-zero CVEs.
This image is available on cgr.dev
:
Be sure to replace the ORGANIZATION
placeholder with the name used for your organization's private repository within the Chainguard registry.
The Chainguard couchdb image is intended to to be a drop-in replacement for the official CouchDB image and is meant to be run with the couchdb Helm chart.
Chainguard's CouchDB image stores its data in /usr/share/couchdb
, with a symbolic link to /opt/couchdb
to provide compatibility with the external image.
The uid/gid for the couchdb
user is 65532
.
The default entrypoint starts the CouchDB server. It needs the username and password to be provided via environment variables.
For example:
To add a volume to persist the data, mount it as /opt/couchdb/data
, like this:
The entrypoint script will provide permissions for the data so that the couchdb
user can read and write to it.
The Chainguard CouchDB image can be used with the CouchDB Helm chart. To use the Chainguard image with the chart, provide the following values to it:
Assuming these values are saved as cgr_values.yaml
, you will be able to run the following to install CouchDB:
By default the image starts as root
user to perform chaning of permissions of storage data and initializing configuration. The couchdb
server is then run as couchdb
user.
It is also possible to run the image (and Helm chart) as couchdb
user. To do it, simply pass -u 65532
flag to docker to specify the userid for couchdb
- such as:
To set the user, group and default filesystem group to couchdb
in the Helm chart, add the following to the values file:
If you have a Zendesk account (typically set up for you by your Customer Success Manager) you can reach out to Chainguard's Customer Success team through our Zendesk portal.
Chainguard Images are a collection of container images designed for security and minimalism.
Many Chainguard Images are distroless; they contain only an open-source application and its runtime dependencies. These images do not even contain a shell or package manager. Chainguard Images are built with Wolfi, our Linux undistro designed to produce container images that meet the requirements of a secure software supply chain.
The main features of Chainguard Images include:
-dev
VariantsAs mentioned previously, Chainguard’s distroless Images have no shell or package manager by default. This is great for security, but sometimes you need these things, especially in builder images. For those cases, most (but not all) Chainguard Images come paired with a -dev
variant which does include a shell and package manager.
Although the -dev
image variants have similar security features as their distroless versions, such as complete SBOMs and signatures, they feature additional software that is typically not necessary in production environments. The general recommendation is to use the -dev
variants only to build the application and then copy all application artifacts into a distroless image, which will result in a final container image that has a minimal attack surface and won’t allow package installations or logins.
That being said, it’s worth noting that -dev
variants of Chainguard Images are completely fine to run in production environments. After all, the -dev
variants are still more secure than many popular container images based on fully-featured operating systems such as Debian and Ubuntu since they carry less software, follow a more frequent patch cadence, and offer attestations for what they include.
To better understand how to work with Chainguard Images, we encourage you to visit Chainguard Academy, our documentation and education platform.
Chainguard Images contain software packages that are direct or transitive dependencies. The following licenses were found in the "latest" version of this image:
Apache-2.0
BSD-3-Clause
GCC-exception-3.1
GPL-2.0-only
GPL-2.0-or-later
GPL-3.0-or-later
LGPL-2.0-or-later
For a complete list of licenses, please refer to this Image's SBOM.
Software license agreement