bitnami/valkey-sentinel repository overview

⁠Bitnami Secure Image for Valkey Sentinel

Overview of Valkey Sentinel⁠ Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.

⁠ TL;DR

docker run --name valkey-sentinel -e VALKEY_PRIMARY_HOST=valkey REGISTRY_NAME/bitnami/valkey-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 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⁠.

⁠ Get this image

The recommended way to get the Bitnami Valkey Sentinel Docker Image is to pull the prebuilt image from the Docker Hub Registry⁠.

docker pull REGISTRY_NAME/bitnami/valkey-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/valkey-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 Valkey 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 Valkey Sentinel instance that will monitor a Valkey 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 Valkey instance

Use the --network app-tier argument to the docker run command to attach the Valkey container to the app-tier network.

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

⁠Step 3: Launch your Valkey Sentinel instance

Finally we create a new container instance to launch the Valkey client and connect to the server created in the previous step:

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

⁠ Configuration

The following section describes the supported environment variables

⁠ Environment variables

The following tables list the main variables you can set.

⁠Customizable environment variables

⁠Read-only environment variables

⁠ Securing Valkey Sentinel traffic

Valkey adds the support for SSL/TLS connections. Should you desire to enable this optional feature, you may use the aforementioned VALKEY_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 VALKEY_SENTINEL_PORT_NUMBER to another port different than 0.

1. Using docker run

   $ docker run --name valkey-sentinel \
       -v /path/to/certs:/opt/bitnami/valkey/certs \
       -v /path/to/valkey-sentinel/persistence:/bitnami \
       -e VALKEY_PRIMARY_HOST=valkey \
       -e VALKEY_SENTINEL_TLS_ENABLED=yes \
       -e VALKEY_SENTINEL_TLS_CERT_FILE=/opt/bitnami/valkey/certs/valkey.crt \
       -e VALKEY_SENTINEL_TLS_KEY_FILE=/opt/bitnami/valkey/certs/valkey.key \
       -e VALKEY_SENTINEL_TLS_CA_FILE=/opt/bitnami/valkey/certs/valkeyCA.crt \
       REGISTRY_NAME/bitnami/valkey-cluster:latest
       REGISTRY_NAME/bitnami/valkey-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/valkey-sentinel/conf/. You can mount a volume at /bitnami and copy/edit the configurations in the /path/to/valkey-persistence/valkey-sentinel/conf/. The default configurations will be populated to the conf/ directory if it's empty.

⁠Step 1: Run the Valkey Sentinel image

Run the Valkey Sentinel image, mounting a directory from your host.

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

⁠Step 2: Edit the configuration

Edit the configuration on your host using your favorite editor.

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

⁠Step 3: Restart Valkey

After changing the configuration, restart your Valkey container for changes to take effect.

docker restart valkey

⁠ FIPS configuration in Bitnami Secure Images

The Bitnami Valkey 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 Valkey Sentinel Docker Image sends the container logs to the stdout. To view the logs:

docker logs valkey

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.

⁠ Notable Changes

⁠ Starting October 20, 2024

• All the references have been updated from master/slave to primary/replica to follow the upstream project strategy. Environment variables previously prefixed as VALKEY_MASTER or VALKEY_SENTINEL_MASTER use VALKEY_PRIMARY and VALKEY_SENTINEL_PRIMARY now.

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