diff --git a/bitnami/redis-cluster/8.6/debian-12/Dockerfile b/bitnami/redis-cluster/8.6/debian-12/Dockerfile index 49dce1392796..653a83ed3848 100644 --- a/bitnami/redis-cluster/8.6/debian-12/Dockerfile +++ b/bitnami/redis-cluster/8.6/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-02-19T04:12:00Z" \ + org.opencontainers.image.created="2026-02-23T12:33:36Z" \ org.opencontainers.image.description="Application packaged by Broadcom, Inc." \ org.opencontainers.image.documentation="https://github.com/bitnami/containers/tree/main/bitnami/redis-cluster/README.md" \ org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/redis-cluster" \ org.opencontainers.image.title="redis-cluster" \ org.opencontainers.image.vendor="Broadcom, Inc." \ - org.opencontainers.image.version="8.6.0" + org.opencontainers.image.version="8.6.1" 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-7-linux-${OS_ARCH}-debian-12" \ - "redis-8.6.0-0-linux-${OS_ARCH}-debian-12" \ + "redis-8.6.1-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/redis-cluster/postunpack.sh -ENV APP_VERSION="8.6.0" \ +ENV APP_VERSION="8.6.1" \ BITNAMI_APP_NAME="redis-cluster" \ - IMAGE_REVISION="1" \ + IMAGE_REVISION="0" \ PATH="/opt/bitnami/common/bin:/opt/bitnami/redis/bin:$PATH" EXPOSE 6379 diff --git a/bitnami/redis-cluster/README.md b/bitnami/redis-cluster/README.md index 16d3075c239f..9ece20f3bde9 100644 --- a/bitnami/redis-cluster/README.md +++ b/bitnami/redis-cluster/README.md @@ -60,105 +60,34 @@ cd bitnami/APP/VERSION/OPERATING-SYSTEM docker build -t bitnami/APP:latest . ``` +## 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/redis-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. For persistence you should mount a directory at the `/bitnami` path. If the mounted directory is empty, it will be initialized on the first run. -```console -docker run \ - -e ALLOW_EMPTY_PASSWORD=yes - -v /path/to/redis-cluster-persistence:/bitnami \ - bitnami/redis-cluster:latest -``` - -You can also do this with a minor change to the [`docker-compose.yml`](https://github.com/bitnami/containers/blob/main/bitnami/redis-cluster/docker-compose.yml) file present in this repository: - -```yaml -redis-cluster: - ... - volumes: - - /path/to/redis-cluster-persistence:/bitnami - ... -``` - ## Connecting to other containers Using [Docker container networking](https://docs.docker.com/engine/userguide/networking/), a different server running inside a container can easily be accessed by your application containers and vice-versa. Containers attached to the same network can communicate with each other using the container name as the hostname. -### Using the Command Line - -#### Step 1: Create a network - -```console -docker network create redis-cluster-network --driver bridge -``` - -#### Step 2: Launch the Redis(R) Cluster container within your network - -Use the `--network ` argument to the `docker run` command to attach the container to the `redis-cluster-network` network. - -```console -docker run -e ALLOW_EMPTY_PASSWORD=yes --name redis-cluster-node1 --network redis-cluster-network bitnami/redis-cluster:latest -``` - -#### Step 3: Run another containers - -We can launch another containers using the same flag (`--network NETWORK`) in the `docker run` command. If you also set a name to your container, you will be able to use it as hostname in your network. - ## Configuration ### Configuration file The image looks for configurations in `/opt/bitnami/redis/mounted-etc/redis.conf`. You can overwrite the `redis.conf` file using your own custom configuration file. -```console -docker run --name redis \ - -e ALLOW_EMPTY_PASSWORD=yes \ - -v /path/to/your_redis.conf:/opt/bitnami/redis/mounted-etc/redis.conf \ - -v /path/to/redis-data-persistence:/bitnami/redis/data \ - bitnami/redis-cluster:latest -``` - -Alternatively, modify the [`docker-compose.yml`](https://github.com/bitnami/containers/blob/main/bitnami/redis/docker-compose.yml) file present in this repository: - -```yaml -services: - redis-node-0: - ... - volumes: - - /path/to/your_redis.conf:/opt/bitnami/redis/mounted-etc/redis.conf - - /path/to/redis-persistence:/bitnami/redis/data - ... -``` - Refer to the [Redis(R) configuration](https://redis.io/topics/config) manual for the complete list of configuration options. ### Overriding configuration Instead of providing a custom `redis.conf`, you may also choose to provide only settings you wish to override. The image will look for `/opt/bitnami/redis/mounted-etc/overrides.conf`. This will be ignored if custom `redis.conf` is provided. -```console -docker run --name redis \ - -e ALLOW_EMPTY_PASSWORD=yes \ - -v /path/to/overrides.conf:/opt/bitnami/redis/mounted-etc/overrides.conf \ - bitnami/redis:latest -``` - -Alternatively, modify the [`docker-compose.yml`](https://github.com/bitnami/containers/blob/main/bitnami/redis/docker-compose.yml) file present in this repository: - -```yaml -services: - redis: - ... - volumes: - - /path/to/overrides.conf:/opt/bitnami/redis/mounted-etc/overrides.conf - ... -``` - ### Environment variables #### Customizable environment variables @@ -228,14 +157,6 @@ services: | `REDIS_DAEMON_GROUP` | Redis system group | `redis` | | `REDIS_DEFAULT_PORT_NUMBER` | Redis port number (Build time) | `6379` | -Once all the Redis(R) nodes are running you need to execute command like the following to initiate the cluster: - -```console -redis-cli --cluster create node1:port node2:port --cluster-replicas 1 --cluster-yes -``` - -Where you can add all the `node:port` that you want. The `--cluster-replicas` parameters indicates how many replicas you want to have for every master. - ### Cluster Initialization Troubleshooting Depending on the environment you're deploying into, you might run into issues where the cluster initialization is not completing successfully. One of the issue is related to the DNS lookup of the redis nodes performed during cluster initialization. By default, this DNS lookup is performed as soon as all the redis nodes reply to a successful ping. @@ -247,68 +168,11 @@ Starting with version 6, Redis(R) adds the support for SSL/TLS connections. Shou When enabling TLS, conventional standard traffic is disabled by default. However this new feature is not mutually exclusive, which means it is possible to listen to both TLS and non-TLS connection simultaneously. To enable non-TLS traffic, set `REDIS_TLS_PORT_NUMBER` to another port different than `0`. -1. Using `docker run` - - ```console - $ docker run --name redis-cluster \ - -v /path/to/certs:/opt/bitnami/redis/certs \ - -v /path/to/redis-cluster-persistence:/bitnami \ - -e ALLOW_EMPTY_PASSWORD=yes \ - -e REDIS_TLS_ENABLED=yes \ - -e REDIS_TLS_CERT_FILE=/opt/bitnami/redis/certs/redis.crt \ - -e REDIS_TLS_KEY_FILE=/opt/bitnami/redis/certs/redis.key \ - -e REDIS_TLS_CA_FILE=/opt/bitnami/redis/certs/redisCA.crt \ - bitnami/redis-cluster:latest - ``` - -2. Modifying the `docker-compose.yml` file present in this repository: - - ```yaml - redis-cluster: - ... - environment: - ... - - REDIS_TLS_ENABLED=yes - - REDIS_TLS_CERT_FILE=/opt/bitnami/redis/certs/redis.crt - - REDIS_TLS_KEY_FILE=/opt/bitnami/redis/certs/redis.key - - REDIS_TLS_CA_FILE=/opt/bitnami/redis/certs/redisCA.crt - ... - volumes: - - /path/to/certs:/opt/bitnami/redis/certs - ... - ... - ``` - Alternatively, you may also provide with this configuration in your [custom](https://github.com/bitnami/containers/blob/main/bitnami/redis-cluster#configuration-file) configuration file. ### Enable Redis(R) Cluster RDB persistence -When the value of `REDIS_RDB_POLICY_DISABLED` is `no` (default value) the Redis(R) default persistence strategy will be used. If you want to modify the default strategy, you can configure it through the `REDIS_RDB_POLICY` parameter. Here is a demonstration of modifying the default persistence strategy - -1. Using `docker run` - - ```console - $ docker run --name redis-cluster \ - -v /path/to/redis-cluster-persistence:/bitnami \ - -e ALLOW_EMPTY_PASSWORD=yes \ - -e REDIS_RDB_POLICY_DISABLED=no - -e REDIS_RDB_POLICY="900#1 600#5 300#10 120#50 60#1000 30#10000" - bitnami/redis-cluster:latest - ``` - -2. Modifying the `docker-compose.yml` file present in this repository: - - ```yaml - redis-cluster: - ... - environment: - ... - - REDIS_TLS_ENABLED=yes - - REDIS_RDB_POLICY_DISABLED=no - - REDIS_RDB_POLICY="900#1 600#5 300#10 120#50 60#1000 30#10000" - ... - ... - ``` +When the value of `REDIS_RDB_POLICY_DISABLED` is `no` (default value) the Redis(R) default persistence strategy will be used. If you want to modify the default strategy, you can configure it through the `REDIS_RDB_POLICY` parameter. ### FIPS configuration in Bitnami Secure Images @@ -326,52 +190,12 @@ docker logs redis-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. -## Maintenance - -### Upgrade this image - -Bitnami provides up-to-date versions of Redis(R) Cluster, including security patches, soon after they are made upstream. We recommend that you follow these steps to upgrade your container. - -#### Step 1: Get the updated image - -```console -docker pull bitnami/redis-cluster:latest -``` - -#### Step 2: Stop the running container - -Stop the currently running container using the command - -```console -docker stop redis-cluster -``` - -#### Step 3: Remove the currently running container - -```console -docker rm -v redis-cluster -``` - -#### Step 4: Run the new image - -Re-create your container from the new image. - -```console -docker run --name redis-cluster bitnami/redis-cluster:latest -``` - ## Upgrading ### To 5.0.12-debian-10-r48 release, 6.2.1-debian-10-r48 release , 6.0.12-debian-10-r48 The cluster initialization logic has changed. Now the container in charge of initialize the cluster will also be part of the cluster. It will initialize Redis in background, create the cluster and then bring back to foreground the Redis process. -## 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/redis-cluster). - -If you detect any issue in the `docker-compose.yaml` file, feel free to report it or contribute with a fix by following our [Contributing Guidelines](https://github.com/bitnami/containers/blob/main/CONTRIBUTING.md). - ## License Copyright © 2026 Broadcom. The term "Broadcom" refers to Broadcom Inc. and/or its subsidiaries.