public_git/bitnami-containers
1
0
Fork 0
mirror of https://github.com/bitnami/containers.git synced 2026-10-17 05:02:41 +02:00
Code Issues Projects Releases Wiki Activity

[bitnami/valkey-cluster] Release 9.0.4-debian-12-r0 (#92807)

Browse Source 
Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>
This commit is contained in:
Bitnami Bot
2026-05-06 07:16:28 +02:00
committed by GitHub
parent 5afc462b00
commit e437d66fa7
2 changed files with 14 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files
bitnami/valkey-cluster/9.0/debian-12/Dockerfile
+5 -5
View File
@@ -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
bitnami/valkey-cluster/README.md
+9 -11
View File
@@ -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