Chainguard Container for openbao

Minimal image with OpenBao.

Chainguard Containers are regularly-updated, secure-by-default container images.

Download this Container Image

For those with access, this container image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/openbao:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

Using openbao

The Chainguard openbao image contains the openbao server binary and supporting config. The image is intended to be a drop-in replacement for the upstream openbao/openbao or openbao images and compatible with the OpenBao Helm chart.

The default entrypoint starts a single-node instance of the server in development mode for testing and development. Note that the container should be given the IPC_LOCK capability.

You can start the container with:

$ docker run --cap-add IPC_LOCK cgr.dev/ORGANIZATION/openbao
==> OpenBao server configuration:

Administrative Namespace:
             Api Address: http://0.0.0.0:8200
                     Cgo: enabled
         Cluster Address: https://0.0.0.0:8201
   Environment Variables: HOME, HOSTNAME, PATH, PWD, SHLVL, SSL_CERT_FILE
              Go Version: go1.23.2
              Listener 1: tcp (addr: "0.0.0.0:8200", cluster address: "0.0.0.0:8201", max_request_duration: "1m30s", max_request_size: "33554432", tls: "disabled")
               Log Level:
           Recovery Mode: false
                 Storage: inmem
                 Version: OpenBao v2.0.2, built '2024-10-10T15:09:44Z'
             Version Sha: 96853bb4de27ab8ffd1b0c2898c691460d43edeb

==> OpenBao server started! Log data will stream in below:
...

To configure openbao for production or other environments, supply a configuration file in the /openbao/config directory e.g:

docker run -v $PWD/openbao.hcl:/openbao/config/openbao.hcl cgr.dev/ORGANIZATION/openbao server

You can also supply config via the BAO_LOCAL_CONFIG variable e.g:

docker run --cap-add=IPC_LOCK -e 'BAO_LOCAL_CONFIG={"storage": {"file": {"path": "/openbao/file"}}, "listener": [{"tcp": { "address": "0.0.0.0:8200", "tls_disable": true}}], "default_lease_ttl": "168h", "max_lease_ttl": "720h", "ui": true}' -p 8200:8200 cgr.dev/chainguard/openbao server

Helm Chart Usage

This image and the openbao-k8s image can be used with the Helm chart. To replace the official images with the Chainguard images, provide the chart with the following values:

injector:
  image:
    registry: "cgr.dev"
    repository: "ORGANIZATION/openbao-k8s"
    tag: "latest"

  agentImage:
    registry: "cgr.dev"
    repository: "ORGANIZATION/openbao"
    tag: "latest"

server:
  image:
    registry: "cgr.dev"
    repository: "ORGANIZATION/openbao"
    tag: "latest"

Assuming these values are saved in cgr_values.yaml, you should be able to run:

helm repo add openbao https://openbao.github.io/openbao-helm
helm install openbao openbao/openbao --values cgr_values.yaml

User

The image starts as root and switches to the lower privileged openbao user in the entrypoint script.

Differences to openbao/openbao image

This image is not identical to the openbao/openbao image. In particular:

• The openbao binary and entrypoint script are stored in /usr/bin
• The underlying OS is Wolfi (which is glibc based) whereas the Openbao image uses Alpine (which is musl based)

This image supports the same environment variables as the openbao/openbao image.

Persisting Storage Data

If using the file data storage plugin, please configure it to write to /openbao/file.

Persisting Logs

By default logs will be streamed to stdout and stderr, but can be configured to write to /openbao/logs.

What are Chainguard Containers?

Chainguard's free tier of Starter container images are built with Wolfi, our minimal Linux undistro.

All other Chainguard Containers are built with Chainguard OS, Chainguard's minimal Linux operating system designed to produce container images that meet the requirements of a more secure software supply chain.

The main features of Chainguard Containers include:

• Minimal design, without unnecessary software bloat
• Daily builds to ensure container images are up-to-date with available security patches
• High quality build-time SBOMs attesting to the provenance of all artifacts within the image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a development, or -dev, variant.

In all other cases, including Chainguard Containers tagged as :latest or with a specific version number, the container images include only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager.

Although the -dev container image variants have similar security features as their more minimal versions, they include additional software that is typically not necessary in production environments. We recommend using multi-stage builds to copy artifacts from the -dev variant into a more minimal production image.

Need additional packages?

To improve security, Chainguard Containers include only essential dependencies. Need more packages? Chainguard customers can use Custom Assembly to add packages, either through the Console, chainctl, or API.

To use Custom Assembly in the Chainguard Console: navigate to the image you'd like to customize in your Organization's list of images, and click on the Customize image button at the top of the page.

Learn More

Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.

Trademarks

This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.