From e437d66fa74cf9255abe5d21b9dfa8e6646a1d97 Mon Sep 17 00:00:00 2001 From: Bitnami Bot Date: Wed, 6 May 2026 07:16:28 +0200 Subject: [PATCH] [bitnami/valkey-cluster] Release 9.0.4-debian-12-r0 (#92807) Signed-off-by: Bitnami Bot --- .../valkey-cluster/9.0/debian-12/Dockerfile | 10 +++++----- bitnami/valkey-cluster/README.md | 20 +++++++++---------- 2 files changed, 14 insertions(+), 16 deletions(-) diff --git a/bitnami/valkey-cluster/9.0/debian-12/Dockerfile b/bitnami/valkey-cluster/9.0/debian-12/Dockerfile index af6a3a6d11d9..780879cbdb0f 100644 --- a/bitnami/valkey-cluster/9.0/debian-12/Dockerfile +++ b/bitnami/valkey-cluster/9.0/debian-12/Dockerfile @@ -7,13 +7,13 @@ ARG DOWNLOADS_URL="downloads.bitnami.com/files/stacksmith" ARG TARGETARCH LABEL org.opencontainers.image.base.name="docker.io/bitnami/minideb:bookworm" \ - org.opencontainers.image.created="2026-04-08T21:49:55Z" \ + org.opencontainers.image.created="2026-05-06T05:07:35Z" \ org.opencontainers.image.description="Application packaged by Broadcom, Inc." \ org.opencontainers.image.documentation="https://github.com/bitnami/containers/tree/main/bitnami/valkey-cluster/README.md" \ org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/valkey-cluster" \ org.opencontainers.image.title="valkey-cluster" \ org.opencontainers.image.vendor="Broadcom, Inc." \ - org.opencontainers.image.version="9.0.3" + org.opencontainers.image.version="9.0.4" ENV HOME="/" \ OS_ARCH="${TARGETARCH:-amd64}" \ @@ -29,7 +29,7 @@ RUN --mount=type=secret,id=downloads_url,env=SECRET_DOWNLOADS_URL \ mkdir -p /tmp/bitnami/pkg/cache/ ; cd /tmp/bitnami/pkg/cache/ || exit 1 ; \ COMPONENTS=( \ "wait-for-port-1.0.10-9-linux-${OS_ARCH}-debian-12" \ - "valkey-9.0.3-3-linux-${OS_ARCH}-debian-12" \ + "valkey-9.0.4-0-linux-${OS_ARCH}-debian-12" \ ) ; \ for COMPONENT in "${COMPONENTS[@]}"; do \ if [ ! -f "${COMPONENT}.tar.gz" ]; then \ @@ -48,9 +48,9 @@ RUN uninstall_packages curl COPY rootfs / RUN /opt/bitnami/scripts/valkey-cluster/postunpack.sh -ENV APP_VERSION="9.0.3" \ +ENV APP_VERSION="9.0.4" \ BITNAMI_APP_NAME="valkey-cluster" \ - IMAGE_REVISION="5" \ + IMAGE_REVISION="0" \ PATH="/opt/bitnami/common/bin:/opt/bitnami/valkey/bin:$PATH" EXPOSE 6379 diff --git a/bitnami/valkey-cluster/README.md b/bitnami/valkey-cluster/README.md index ed2c3a9f3053..dce6946b3507 100644 --- a/bitnami/valkey-cluster/README.md +++ b/bitnami/valkey-cluster/README.md @@ -11,6 +11,14 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema docker run --name valkey-cluster -e ALLOW_EMPTY_PASSWORD=yes bitnami/valkey-cluster:latest ``` +## Using `docker-compose.yml` + +The docker-compose.yaml file of this container can be found in the [Bitnami Containers repository](https://github.com/bitnami/containers/). + +[https://github.com/bitnami/containers/tree/main/bitnami/valkey-cluster/docker-compose.yml](https://github.com/bitnami/containers/tree/main/bitnami/valkey-cluster/docker-compose.yml) + +Please be aware this file has not undergone internal testing. Consequently, we advise its use exclusively for development or testing purposes. For production-ready deployments, we highly recommend utilizing its associated [Bitnami Helm chart](https://github.com/bitnami/charts/tree/main/bitnami/valkey-cluster). + ## Why use Bitnami Secure Images? Those are hardened, minimal CVE images built and maintained by Bitnami. Bitnami Secure Images are based on the cloud-optimized, security-hardened enterprise [OS Photon Linux](https://vmware.github.io/photon/). Why choose BSI images? @@ -40,10 +48,6 @@ Learn more about the Bitnami tagging policy and the difference between rolling t The Bitnami Valkey Cluster Docker image is only available to [Bitnami Secure Images](https://bitnami.com) customers. -## Using `docker-compose.yaml` - -Please be aware this file has not undergone internal testing. Consequently, we advise its use exclusively for development or testing purposes. For production-ready deployments, we highly recommend utilizing its associated [Bitnami Helm chart](https://github.com/bitnami/charts/tree/main/bitnami/valkey-cluster). - ## Persisting your application If you remove the container all your data will be lost, and the next time you run the image the database will be reinitialized. To avoid this loss of data, you should mount a volume that will persist even after the container is removed. @@ -164,13 +168,7 @@ The Bitnami Valkey Cluster Docker image from the [Bitnami Secure Images](https:/ ## Logging -The Bitnami Valkey Cluster Docker image sends the container logs to `stdout`. To view the logs: - -```console -docker logs valkey-cluster -``` - -You can configure the containers [logging driver](https://docs.docker.com/engine/admin/logging/overview/) using the `--log-driver` option if you wish to consume the container logs differently. In the default configuration docker uses the `json-file` driver. +The Bitnami Valkey Cluster Docker image sends the container logs to the `stdout`. You can configure the containers [logging driver](https://docs.docker.com/engine/admin/logging/overview/) using the `--log-driver` option if you wish to consume the container logs differently. In the default configuration docker uses the `json-file` driver. ## Notable Changes