Chainguard Image for redis-bitnami

Minimalist Wolfi-based Redis-Bitnami image.

Chainguard Images are regularly-updated, minimal container images with low-to-zero CVEs.

Download this Image

This image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/redis-bitnami:latest

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

Compatibility Notes

Redis is an in-memory key-value database. Chainguard's redis-bitnami container images are comparable to the bitnami/redis image available on Docker Hub. However, the Chainguard images contain only the minimum set of tools and dependencies needed to function. This means it does not include things like a shell or a package manager.

Redis Bitnami Images:

The redis-bitnami images are intended to be drop-in replacements for deployments that require Bitnami compatibility. The redis-bitnami image actually contains three images:

redis-server-bitnami

The redis-server-bitnami image contains the Redis server software with Bitnami compatibility. Redis is an in-memory key-value database often used as a cache, vector database, document database, streaming engine, and message broker. It comes with its own commands and APIs which allow you to interact with and manage your Redis data.

redis-cluster-bitnami

redis-cluster-bitnami contains a Bitnami-compatible version of Redis Cluster, a distributed implementation of Redis. This allows you to run multiple Redis nodes that write to the same database with high performance, high availability, and an acceptable degree of write safety. Redis Cluster can support up to 1000 nodes.

redis-sentinel-bitnami

redis-sentinel-bitnami contains a Bitnami-compatible version of Redis Sentinel, a version of Redis that provides high availability and other collateral tasks such as monitoring, notifications, and acts as a configuration provider for clients.

Deploying with Helm

The most common deployment case is to use the Bitnami Helm chart, which can be deployed as follows:

cat <<EOF > values.yaml
image:
  registry: cgr.dev
  repository: ORGANIZATION/redis-server-bitnami
  tag: latest
# Optionally enable HA sentinel:
sentinel:
  enabled: true
  image:
    registry: cgr.dev
    repository: ORGANIZATION/redis-sentinel-bitnami
    tag: latest
# Optionally enable Redis cluster:
cluster:
  enabled: true
  image:
    registry: cgr.dev
    repository: ORGANIZATION/redis-cluster-bitnami
    tag: latest
EOF

Contact Support

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.

What are Chainguard Images?

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:

• Minimal design, with no unnecessary software bloat
• Automated nightly builds to ensure Images are completely up-to-date and contain all available security patches
• High quality build-time SBOMs (software bills of materials) attesting the provenance of all artifacts within the Image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

-dev Variants

As 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.

Learn More

To better understand how to work with Chainguard Images, we encourage you to visit Chainguard Academy, our documentation and education platform.