bitnami/redis-sentinel repository overview

⁠Bitnami Secure Image for Redis® Sentinel

⁠What is Redis® Sentinel?

Overview of Redis® Sentinel⁠ Disclaimer: Redis is a registered trademark of Redis Ltd. Any rights therein are reserved to Redis Ltd. Any use by Bitnami is for referential purposes only and does not indicate any sponsorship, endorsement, or affiliation between Redis Ltd.

⁠TL;DR

docker run --name redis-sentinel -e REDIS_MASTER_HOST=redis REGISTRY_NAME/bitnami/redis-sentinel:latest

Warning: This quick setup is only intended for development environments. You are encouraged to change the insecure default credentials and check out the available configuration options in the Environment Variables⁠ section for a more secure deployment.

⁠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⁠. Why choose BSI images?

• Hardened secure images of popular open source software with Near-Zero Vulnerabilities
• Vulnerability Triage & Prioritization with VEX Statements, KEV and EPSS Scores
• Compliance focus with FIPS, STIG, and air-gap options, including secure bill of materials (SBOM)
• Software supply chain provenance attestation through in-toto
• First class support for the internet’s favorite Helm charts

Each image comes with valuable security metadata. You can view the metadata in our public catalog here⁠. Note: Some data is only available with commercial subscriptions to BSI⁠.

If you are looking for our previous generation of images based on Debian Linux, please see the Bitnami Legacy registry⁠.

⁠Why use a non-root container?

Non-root container images add an extra layer of security and are generally recommended for production environments. However, because they run as a non-root user, privileged tasks are typically off-limits. Learn more about non-root containers in our docs⁠.

⁠Supported tags and respective Dockerfile links

Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags in our documentation page⁠.

You can see the equivalence between the different tags by taking a look at the tags-info.yaml file present in the branch folder, i.e bitnami/ASSET/BRANCH/DISTRO/tags-info.yaml.

Subscribe to project updates by watching the bitnami/containers GitHub repo⁠.

⁠Get this image

The recommended way to get the Bitnami Redis(R) Sentinel Docker Image is to pull the prebuilt image from the Docker Hub Registry⁠.

docker pull REGISTRY_NAME/bitnami/redis-sentinel:latest

To use a specific version, you can pull a versioned tag. You can view the list of available versions⁠ in the Docker Hub Registry.

docker pull REGISTRY_NAME/bitnami/redis-sentinel:[TAG]

If you wish, you can also build the image yourself by cloning the repository, changing to the directory containing the Dockerfile and executing the docker build command. Remember to replace the APP, VERSION and OPERATING-SYSTEM path placeholders in the example command below with the correct values.

git clone https://github.com/bitnami/containers.git
cd bitnami/APP/VERSION/OPERATING-SYSTEM
docker build -t REGISTRY_NAME/bitnami/APP:latest .

⁠Connecting to other containers

Using Docker container networking⁠, a Redis(R) server running inside a container can easily be accessed by your application containers.

Containers attached to the same network can communicate with each other using the container name as the hostname.

⁠Using the Command Line

In this example, we will create a Redis(R) Sentinel instance that will monitor a Redis(R) instance that is running on the same docker network.

⁠Step 1: Create a network

docker network create app-tier --driver bridge

⁠Step 2: Launch the Redis(R) instance

Use the --network app-tier argument to the docker run command to attach the Redis(R) container to the app-tier network.

docker run -d --name redis-server \
    -e ALLOW_EMPTY_PASSWORD=yes \
    --network app-tier \
    REGISTRY_NAME/bitnami/redis:latest

⁠Step 3: Launch your Redis(R) Sentinel instance

Finally we create a new container instance to launch the Redis(R) client and connect to the server created in the previous step:

docker run -it --rm \
    -e REDIS_MASTER_HOST=redis-server \
    --network app-tier \
    REGISTRY_NAME/bitnami/redis-sentinel:latest

⁠Configuration

⁠Environment variables

⁠Customizable environment variables

⁠Read-only environment variables

⁠Securing Redis(R) Sentinel traffic

Starting with version 6, Redis(R) adds the support for SSL/TLS connections. Should you desire to enable this optional feature, you may use the aforementioned REDIS_SENTINEL_TLS_* environment variables to configure the application.

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_SENTINEL_PORT_NUMBER to another port different than 0.

1. Using docker run

   $ docker run --name redis-sentinel \
       -v /path/to/certs:/opt/bitnami/redis/certs \
       -v /path/to/redis-sentinel/persistence:/bitnami \
       -e REDIS_MASTER_HOST=redis \
       -e REDIS_SENTINEL_TLS_ENABLED=yes \
       -e REDIS_SENTINEL_TLS_CERT_FILE=/opt/bitnami/redis/certs/redis.crt \
       -e REDIS_SENTINEL_TLS_KEY_FILE=/opt/bitnami/redis/certs/redis.key \
       -e REDIS_SENTINEL_TLS_CA_FILE=/opt/bitnami/redis/certs/redisCA.crt \
       REGISTRY_NAME/bitnami/redis-cluster:latest
       REGISTRY_NAME/bitnami/redis-sentinel:latest
   

   Copy

Alternatively, you may also provide with this configuration in your custom⁠ configuration file.

⁠Configuration file

The image looks for configurations in /bitnami/redis-sentinel/conf/. You can mount a volume at /bitnami and copy/edit the configurations in the /path/to/redis-persistence/redis-sentinel/conf/. The default configurations will be populated to the conf/ directory if it's empty.

⁠Step 1: Run the Redis(R) Sentinel image

Run the Redis(R) Sentinel image, mounting a directory from your host.

docker run --name redis-sentinel \
    -e REDIS_MASTER_HOST=redis \
    -v /path/to/redis-sentinel/persistence:/bitnami \
    REGISTRY_NAME/bitnami/redis-sentinel:latest

⁠Step 2: Edit the configuration

Edit the configuration on your host using your favorite editor.

vi /path/to/redis-persistence/redis-sentinel/conf/redis.conf

⁠Step 3: Restart Redis(R)

After changing the configuration, restart your Redis(R) container for changes to take effect.

docker restart redis

Refer to the Redis(R) configuration⁠ manual for the complete list of configuration options.

⁠FIPS configuration in Bitnami Secure Images

The Bitnami Redis® Sentinel Docker image from the Bitnami Secure Images⁠ catalog includes extra features and settings to configure the container with FIPS capabilities. You can configure the next environment variables:

• OPENSSL_FIPS: whether OpenSSL runs in FIPS mode or not. yes (default), no.

⁠Logging

The Bitnami Redis(R) Sentinel Docker Image sends the container logs to the stdout. To view the logs:

docker logs redis

You can configure the containers logging driver⁠ 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) Sentinel, 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

docker pull REGISTRY_NAME/bitnami/redis-sentinel:latest

⁠Step 2: Stop and backup the currently running container

Stop the currently running container using the command

docker stop redis

Next, take a snapshot of the persistent volume /path/to/redis-persistence using:

rsync -a /path/to/redis-persistence /path/to/redis-persistence.bkp.$(date +%Y%m%d-%H.%M.%S)

⁠Step 3: Remove the currently running container

docker rm -v redis

⁠Step 4: Run the new image

Re-create your container from the new image.

docker run --name redis REGISTRY_NAME/bitnami/redis-sentinel:latest

⁠Notable Changes

⁠Starting January 16, 2024

• The docker-compose.yaml file has been removed, as it was solely intended for internal testing purposes.

⁠4.0.14-debian-9-r201, 4.0.14-ol-7-r222, 5.0.5-debian-9-r169, 5.0.5-ol-7-r175

• Decrease the size of the container. The configuration logic is now based on Bash scripts in the rootfs/ folder.

⁠4.0.10-r25

• The Redis(R) sentinel container has been migrated to a non-root container approach. Previously the container run as root user and the redis daemon was started as redis user. From now own, both the container and the redis daemon run as user 1001. As a consequence, the configuration files are writable by the user running the redis process. You can revert this behavior by changing USER 1001 to USER root in the Dockerfile.

⁠Contributing

We'd love for you to contribute to this container. You can request new features by creating an issue⁠ or submitting a pull request⁠ with your contribution.

⁠Issues

If you encountered a problem running this container, you can file an issue⁠. For us to provide better support, be sure to fill the issue template.

⁠License

Copyright © 2026 Broadcom. The term "Broadcom" refers to Broadcom Inc. and/or its subsidiaries.

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0⁠

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.