bitnami/valkey repository overview

⁠Bitnami Secure Image for Valkey

Overview of Valkey⁠ 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 -e ALLOW_EMPTY_PASSWORD=yes REGISTRY_NAME/bitnami/valkey:latest

Warning: These quick setups are only intended for development environments. You are encouraged to change the insecure default credentials and check out the available configuration options in the Configuration⁠ section for a more secure deployment.

⁠ How to deploy Valkey in Kubernetes?

Deploying Bitnami applications as Helm Charts is the easiest way to get started with our applications on Kubernetes. Read more about the installation in the Bitnami Valkey Chart GitHub repository⁠.

⁠ 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 Docker Image is to pull the prebuilt image from the Docker Hub Registry⁠.

docker pull REGISTRY_NAME/bitnami/valkey: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:[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 .

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

⁠ Persisting your database

Valkey provides a different range of persistence options⁠. This contanier uses AOF persistence by default but it is easy to overwrite that configuration in a docker-compose.yaml file with this entry command: /opt/bitnami/scripts/valkey/run.sh --appendonly no. Alternatively, you may use the VALKEY_AOF_ENABLED env variable as explained in Disabling AOF persistence⁠.

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.

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

⁠ 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

⁠ Disabling Valkey commands

For security reasons, you may want to disable some commands. You can specify them by using the following environment variable on the first run:

• VALKEY_DISABLE_COMMANDS: Comma-separated list of Valkey commands to disable. Defaults to empty.

⁠ Passing extra command-line flags to valkey-server startup

Passing extra command-line flags to the valkey service command is possible by adding them as arguments to run.sh script:

docker run --name valkey -e ALLOW_EMPTY_PASSWORD=yes REGISTRY_NAME/bitnami/valkey:latest /opt/bitnami/scripts/valkey/run.sh --maxmemory 100mb

Alternatively, modify the docker-compose.yml⁠ file present in this repository:

services:
  valkey:
  ...
    environment:
      - ALLOW_EMPTY_PASSWORD=yes
    command: /opt/bitnami/scripts/valkey/run.sh --maxmemory 100mb
  ...

⁠ Setting the server password on first run

Passing the VALKEY_PASSWORD environment variable when running the image for the first time will set the Valkey server password to the value of VALKEY_PASSWORD (or the content of the file specified in VALKEY_PASSWORD_FILE).

NOTE: The at sign (@) is not supported for VALKEY_PASSWORD.

Warning The Valkey database is always configured with remote access enabled. It's suggested that the VALKEY_PASSWORD env variable is always specified to set a password. In case you want to access the database without a password set the environment variable ALLOW_EMPTY_PASSWORD=yes. This is recommended only for development.

⁠ Allowing empty passwords

By default the Valkey image expects all the available passwords to be set. In order to allow empty passwords, it is necessary to set the ALLOW_EMPTY_PASSWORD=yes env variable. This env variable is only recommended for testing or development purposes. We strongly recommend specifying the VALKEY_PASSWORD for any other scenario.

⁠ Disabling AOF persistence

Valkey offers different options⁠ when it comes to persistence. By default, this image is set up to use the AOF (Append Only File) approach. Should you need to change this behaviour, setting the VALKEY_AOF_ENABLED=no env variable will disable this feature.

⁠ Enabling Access Control List

Valkey offers ACL⁠ which allows certain connections to be limited in terms of the commands that can be executed and the keys that can be accessed. We strongly recommend enabling ACL in production by specifying the VALKEY_ACLFILE.

docker run -name valkey -e VALKEY_ACLFILE=/opt/bitnami/valkey/mounted-etc/users.acl -v /path/to/users.acl:/opt/bitnami/valkey/mounted-etc/users.acl REGISTRY_NAME/bitnami/valkey:latest

Alternatively, modify the docker-compose.yml⁠ file present in this repository:

services:
  valkey:
  ...
    environment:
      - VALKEY_ACLFILE=/opt/bitnami/valkey/mounted-etc/users.acl
    volumes:
      - /path/to/users.acl:/opt/bitnami/valkey/mounted-etc/users.acl
  ...

⁠ Setting up a standalone instance

By default, this image is set up to launch Valkey in standalone mode on port 6379. Should you need to change this behavior, setting the VALKEY_PORT_NUMBER environment variable will modify the port number. This is not to be confused with VALKEY_PRIMARY_PORT_NUMBER or VALKEY_REPLICA_PORT environment variables that are applicable in replication mode.

⁠ Setting up replication

A replication cluster can easily be setup with the Bitnami Valkey Docker Image using the following environment variables:

• VALKEY_REPLICATION_MODE: The replication mode. Possible values primary/replica. No defaults.
• VALKEY_REPLICA_IP: The replication announce ip. Defaults to $(get_machine_ip) which return the ip of the container.
• VALKEY_REPLICA_PORT: The replication announce port. Defaults to VALKEY_PRIMARY_PORT_NUMBER.
• VALKEY_PRIMARY_HOST: Hostname/IP of replication primary (replica node parameter). No defaults.
• VALKEY_PRIMARY_PORT_NUMBER: Server port of the replication primary (replica node parameter). Defaults to 6379.
• VALKEY_PRIMARY_PASSWORD: Password to authenticate with the primary (replica node parameter). No defaults. As an alternative, you can mount a file with the password and set the VALKEY_PRIMARY_PASSWORD_FILE variable.

In a replication cluster you can have one primary and zero or more replicas. When replication is enabled the primary node is in read-write mode, while the replicas are in read-only mode. For best performance its advisable to limit the reads to the replicas.

⁠ Securing Valkey traffic

Valkey adds the support for SSL/TLS connections. Should you desire to enable this optional feature, you may use the following environment variables to configure the application:

• VALKEY_TLS_ENABLED: Whether to enable TLS for traffic or not. Defaults to no.
• VALKEY_TLS_PORT_NUMBER: Port used for TLS secure traffic. Defaults to 6379.
• VALKEY_TLS_CERT_FILE: File containing the certificate file for the TLS traffic. No defaults.
• VALKEY_TLS_KEY_FILE: File containing the key for certificate. No defaults.
• VALKEY_TLS_CA_FILE: File containing the CA of the certificate (takes precedence over VALKEY_TLS_CA_DIR). No defaults.
• VALKEY_TLS_CA_DIR: Directory containing the CA certificates. No defaults.
• VALKEY_TLS_DH_PARAMS_FILE: File containing DH params (in order to support DH based ciphers). No defaults.
• VALKEY_TLS_AUTH_CLIENTS: Whether to require clients to authenticate or not. Defaults to yes.

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

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

⁠ Configuration file

The image looks for configurations in /opt/bitnami/valkey/mounted-etc/valkey.conf. You can overwrite the valkey.conf file using your own custom configuration file.

docker run --name valkey \
    -e ALLOW_EMPTY_PASSWORD=yes \
    -v /path/to/your_valkey.conf:/opt/bitnami/valkey/mounted-etc/valkey.conf \
    -v /path/to/valkey-data-persistence:/bitnami/valkey/data \
    REGISTRY_NAME/bitnami/valkey:latest

Alternatively, modify the docker-compose.yml⁠ file present in this repository:

services:
  valkey:
  ...
    volumes:
      - /path/to/your_valkey.conf:/opt/bitnami/valkey/mounted-etc/valkey.conf
      - /path/to/valkey-persistence:/bitnami/valkey/data
  ...

⁠ Overriding configuration

Instead of providing a custom valkey.conf, you may also choose to provide only settings you wish to override. The image will look for /opt/bitnami/valkey/mounted-etc/overrides.conf. This will be ignored if custom valkey.conf is provided.

docker run --name valkey \
    -e ALLOW_EMPTY_PASSWORD=yes \
    -v /path/to/overrides.conf:/opt/bitnami/valkey/mounted-etc/overrides.conf \
    REGISTRY_NAME/bitnami/valkey:latest

Alternatively, modify the docker-compose.yml⁠ file present in this repository:

services:
  valkey:
  ...
    volumes:
      - /path/to/overrides.conf:/opt/bitnami/valkey/mounted-etc/overrides.conf
  ...

⁠ Enable Valkey RDB persistence

When the value of VALKEY_RDB_POLICY_DISABLED is no (default value) the Valkey default persistence strategy will be used. If you want to modify the default strategy, you can configure it through the VALKEY_RDB_POLICY parameter.

⁠ FIPS configuration in Bitnami Secure Images

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

docker logs valkey

or using Docker Compose:

docker-compose 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.