A newer version of this documentation is available.

View Latest

Frequently Asked Questions about Couchbase Containers

      Frequently asked questions about Couchbase Containers

      Do we support modifying the official Couchbase container?

      No. The official Couchbase container images on DockerHub and Red Hat Registry are actual binaries which get built with our Dockerfile, which consists of commands to assemble the image and some best practices.

      The Couchbase containers are published with the automated build flag turned on and will automatically be rebuilt and updated when new vulnerabilities are detected or when new versions of the base OS image is available.

      Do we support custom containers, that is, containers not based on the official Couchbase container?

      Yes, we support modifying the Dockerfile to build a customized Couchbase container image.

      Customizing Couchbase container images by updating and rebuilding the Dockerfile with your environment-specific settings or best practice guidelines, and not changing or altering the Couchbase binaries is supported.

      Can we provide alternative containers with different base operating systems?

      We currently support the following base operating systems: * Ubuntu for DockerHub * RHEL for Red Hat Registry

      Are there any restrictions on using a container we make for OpenShift/RHCC in a non-OpenShift environment?

      The official Couchbase image for Red Hat Catalog is built with Red Hat Enterprise Linux (RHEL) as the base OS. There are no restrictions on the usage of the image itself.

      Do we support Kubernetes deployments that do not use Couchbase Autonomous Operator?

      If you are considering deploying and running Couchbase Server on the Kubernetes platform, we highly recommend using Couchbase Autonomous Operator. However, if you choose to deploy Couchbase Server on the Kubernetes platform on your own, note that Couchbase will only support Couchbase Server product issues and the container images.