[{"_1":2,"_144":-5,"_145":-5},"loaderData",{"_3":4,"_13":14,"_21":22,"_138":139},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","routes/_layout",{"_15":-5,"_16":17,"_18":17,"_19":11,"_20":11},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","showHoneypotTrap","routes/_layout.layers.$namespace.$reponame.$tag.(images).($imageUrlDigest)",{"_23":24,"_25":26,"_55":56,"_57":-7,"_58":-7,"_59":-7,"_60":-7,"_61":-5,"_62":-5,"_63":11,"_64":11,"_48":65,"_128":17,"_95":96,"_129":94,"_130":47,"_31":32,"_131":11,"_132":17,"_133":134,"_135":-5,"_136":11,"_137":11},"scanningType","none","tagData",{"_27":28,"_29":30,"_31":32,"_33":34,"_35":36,"_37":38,"_39":40,"_41":30,"_42":43,"_44":45,"_46":47,"_48":49,"_50":-5,"_51":40,"_52":53,"_54":17},"content_type","unrecognized","creator",35095401,"digest","sha256:56dbb4bfe1cfe244cc5e23d461efcfc7a1c9820af814ebbcfd0a25e5c2654bed","full_size",1282161,"id",1294944673,"images",[],"last_updated","2026-09-03T23:42:05.20261Z","last_updater","last_updater_username","bitnamibot508","media_type","application/vnd.vmware.tac.metadata.config.v1+json","name","sha256-b330d587970c5925265a12d367feba4b6cd89078c75ba118ffb70002834c1a7c.metadata","repository",24038992,"tag_last_pulled","tag_last_pushed","tag_status","active","v2","tagImages",[],"layerOrdinals","packageName","cveId","sbom","scoutSummary","staticSummary","isScoutPaymentRequired","canSeeVulnerabilities",{"_66":67,"_78":79,"_81":82,"_83":84,"_85":11,"_39":86,"_87":88,"_89":90,"_46":94,"_95":96,"_97":98,"_99":80,"_100":101,"_102":103,"_104":53,"_105":-5,"_106":107,"_108":109,"_110":11,"_111":112,"_113":114,"_119":11,"_120":121,"_125":96,"_126":127},"categories",[68,72,75],{"_46":69,"_70":71},"Message queues","slug","message-queues",{"_46":73,"_70":74},"Databases & storage","databases-and-storage",{"_46":76,"_70":77},"Monitoring & observability","monitoring-and-observability","content_types",[80,28],"image","date_registered","2024-05-07T16:44:18.859051Z","description","Bitnami Secure Image for valkey","is_private","2026-09-19T16:03:52.880533Z","last_modified","2026-09-22T08:06:59.750219Z","media_types",[91,92,93,45],"application/vnd.docker.distribution.manifest.list.v2+json","application/vnd.oci.image.config.v1+json","application/vnd.oci.image.index.v1+json","valkey","namespace","bitnami","pull_count",2641337,"repository_type","star_count",5,"status",1,"status_description","source","collaborator_count",0,"full_description","# Bitnami Secure Image for Valkey\n\n> Valkey is a high-performance data structure server that primarily serves key/value workloads. It supports a wide range of native structures and an extensible plugin system for adding new data structures and access patterns.\n\n[Overview of Valkey](https://valkey.io/)\nTrademarks: 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.\n\n## TL;DR\n\n```console\ndocker run --name valkey REGISTRY_NAME/bitnami/valkey:latest\n```\n\n> Note: You need to substitute the `REGISTRY_NAME` placeholder with a reference to your container registry.\n\n## Using `docker-compose.yml`\n\nThe docker-compose.yaml file of this container can be found in the [Bitnami Containers repository](https://github.com/bitnami/containers/).\n\n[https://github.com/bitnami/containers/tree/main/bitnami/valkey/docker-compose.yml](https://github.com/bitnami/containers/tree/main/bitnami/valkey/docker-compose.yml)\n\nPlease 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).\n\n## How to deploy Valkey in Kubernetes?\n\nDeploying 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](https://github.com/bitnami/charts/tree/master/bitnami/valkey).\n\n## Why use a non-root container?\n\nNon-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](https://techdocs.broadcom.com/us/en/vmware-tanzu/application-catalog/tanzu-application-catalog/services/tac-doc/apps-tutorials-work-with-non-root-containers-index.html).\n\n## Supported tags and respective `Dockerfile` links\n\nLearn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags [in our documentation page](https://techdocs.broadcom.com/us/en/vmware-tanzu/application-catalog/tanzu-application-catalog/services/tac-doc/apps-tutorials-understand-rolling-tags-containers-index.html).\n\n## Get this image\n\nThe Bitnami Valkey Docker image is only available to [Bitnami Secure Images](https://bitnami.com) customers.\n\n## Persisting your database\n\nValkey provides a different range of [persistence options](https://valkey.io/docs/topics/persistence.html). This contanier uses *AOF persistence by default* but it is easy to overwrite that configuration by setting the following command when running the container `/opt/bitnami/scripts/valkey/run.sh --appendonly no`. Alternatively, you may use the `VALKEY_AOF_ENABLED` env variable as explained in [Disabling AOF persistence](https://github.com/bitnami/containers/blob/main/bitnami/valkey#disabling-aof-persistence).\n\nIf 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.\n\nFor persistence you should mount a directory at the `/bitnami` path. If the mounted directory is empty, it will be initialized on the first run.\n\n> **NOTE** As this is a non-root container, the mounted files and directories must have the proper permissions for the UID `1001`.\n\n## Connecting to other containers\n\nUsing [Docker container networking](https://docs.docker.com/engine/userguide/networking/), a Valkey server running inside a container can easily be accessed by your application containers.\n\nContainers attached to the same network can communicate with each other using the container name as the hostname.\n\n## Configuration\n\nThe following section describes the supported environment variables\n\n### Environment variables\n\nThe following tables list the main variables you can set.\n\n#### Customizable environment variables\n\n| Name | Description | Default Value |\n|-----------------------------------|----------------------------------------------------|---------------------------------------------|\n| `VALKEY_DATA_DIR` | Valkey data directory | `${VALKEY_VOLUME_DIR}/data` |\n| `VALKEY_OVERRIDES_FILE` | Valkey config overrides file | `${VALKEY_MOUNTED_CONF_DIR}/overrides.conf` |\n| `VALKEY_DISABLE_COMMANDS` | Commands to disable in Valkey | `nil` |\n| `VALKEY_DATABASE` | Default Valkey database | `valkey` |\n| `VALKEY_AOF_ENABLED` | Enable AOF | `yes` |\n| `VALKEY_RDB_POLICY` | Enable RDB policy persistence | `nil` |\n| `VALKEY_RDB_POLICY_DISABLED` | Allows to enable RDB policy persistence | `no` |\n| `VALKEY_PRIMARY_HOST` | Valkey primary host (used by replicas) | `nil` |\n| `VALKEY_PRIMARY_PORT_NUMBER` | Valkey primary host port (used by replicas) | `6379` |\n| `VALKEY_PORT_NUMBER` | Valkey port number | `$VALKEY_DEFAULT_PORT_NUMBER` |\n| `VALKEY_ALLOW_REMOTE_CONNECTIONS` | Allow remote connection to the service | `yes` |\n| `VALKEY_REPLICATION_MODE` | Valkey replication mode (values: primary, replica) | `nil` |\n| `VALKEY_REPLICA_IP` | The replication announce ip | `nil` |\n| `VALKEY_REPLICA_PORT` | The replication announce port | `nil` |\n| `VALKEY_EXTRA_FLAGS` | Additional flags pass to 'valkey-server' commands | `nil` |\n| `ALLOW_EMPTY_PASSWORD` | Allow password-less access | `no` |\n| `VALKEY_PASSWORD` | Password for Valkey | `nil` |\n| `VALKEY_PRIMARY_PASSWORD` | Valkey primary node password | `nil` |\n| `VALKEY_ACLFILE` | Valkey ACL file | `nil` |\n| `VALKEY_IO_THREADS_DO_READS` | Enable multithreading when reading socket | `nil` |\n| `VALKEY_IO_THREADS` | Number of threads | `nil` |\n| `VALKEY_TLS_ENABLED` | Enable TLS | `no` |\n| `VALKEY_TLS_PORT_NUMBER` | Valkey TLS port (requires VALKEY_ENABLE_TLS=yes) | `6379` |\n| `VALKEY_TLS_CERT_FILE` | Valkey TLS certificate file | `nil` |\n| `VALKEY_TLS_CA_DIR` | Directory containing TLS CA certificates | `nil` |\n| `VALKEY_TLS_KEY_FILE` | Valkey TLS key file | `nil` |\n| `VALKEY_TLS_KEY_FILE_PASS` | Valkey TLS key file passphrase | `nil` |\n| `VALKEY_TLS_CA_FILE` | Valkey TLS CA file | `nil` |\n| `VALKEY_TLS_DH_PARAMS_FILE` | Valkey TLS DH parameter file | `nil` |\n| `VALKEY_TLS_AUTH_CLIENTS` | Enable Valkey TLS client authentication | `yes` |\n| `VALKEY_SENTINEL_PRIMARY_NAME` | Valkey Sentinel primary name | `nil` |\n| `VALKEY_SENTINEL_HOST` | Valkey Sentinel host | `nil` |\n| `VALKEY_SENTINEL_PORT_NUMBER` | Valkey Sentinel host port (used by replicas) | `26379` |\n| `VALKEY_SENTINEL_PASSWORD` | Valkey Sentinel password | `nil` |\n\n#### Read-only environment variables\n\n| Name | Description | Value |\n|------------------------------|----------------------------------------|----------------------------------|\n| `VALKEY_VOLUME_DIR` | Persistence base directory | `/bitnami/valkey` |\n| `VALKEY_BASE_DIR` | Valkey installation directory | `${BITNAMI_ROOT_DIR}/valkey` |\n| `VALKEY_CONF_DIR` | Valkey configuration directory | `${VALKEY_BASE_DIR}/etc` |\n| `VALKEY_DEFAULT_CONF_DIR` | Valkey default configuration directory | `${VALKEY_BASE_DIR}/etc.default` |\n| `VALKEY_MOUNTED_CONF_DIR` | Valkey mounted configuration directory | `${VALKEY_BASE_DIR}/mounted-etc` |\n| `VALKEY_CONF_FILE` | Valkey configuration file | `${VALKEY_CONF_DIR}/valkey.conf` |\n| `VALKEY_LOG_DIR` | Valkey logs directory | `${VALKEY_BASE_DIR}/logs` |\n| `VALKEY_LOG_FILE` | Valkey log file | `${VALKEY_LOG_DIR}/valkey.log` |\n| `VALKEY_TMP_DIR` | Valkey temporary directory | `${VALKEY_BASE_DIR}/tmp` |\n| `VALKEY_PID_FILE` | Valkey PID file | `${VALKEY_TMP_DIR}/valkey.pid` |\n| `VALKEY_BIN_DIR` | Valkey executables directory | `${VALKEY_BASE_DIR}/bin` |\n| `VALKEY_DAEMON_USER` | Valkey system user | `valkey` |\n| `VALKEY_DAEMON_GROUP` | Valkey system group | `valkey` |\n| `VALKEY_DEFAULT_PORT_NUMBER` | Valkey port number (Build time) | `6379` |\n\n### Disabling Valkey commands\n\nFor security reasons, you may want to disable some commands. You can specify them by using the following environment variable on the first run:\n\n- `VALKEY_DISABLE_COMMANDS`: Comma-separated list of Valkey commands to disable. Defaults to empty.\n\n### Passing extra command-line flags to valkey-server startup\n\nPassing extra command-line flags to the valkey service command is possible by adding them as arguments to *run.sh* script:\n\n```console\ndocker run --name valkey -e ALLOW_EMPTY_PASSWORD=yes REGISTRY_NAME/bitnami/valkey:latest /opt/bitnami/scripts/valkey/run.sh --maxmemory 100mb\n```\n\n### Setting the server password on first run\n\nPassing 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`).\n\n**NOTE**: The at sign (`@`) is not supported for `VALKEY_PASSWORD`.\n\n**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**.\n\n### Allowing empty passwords\n\nBy 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.\n\n### Disabling AOF persistence\n\nValkey offers different [options](https://valkey.io/docs/topics/persistence.html) 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.\n\n### Enabling Access Control List\n\nValkey offers [ACL](https://valkey.io/docs/topics/acl.html) 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`.\n\n```console\ndocker 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\n```\n\n### Setting up a standalone instance\n\nBy 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.\n\n### Setting up replication\n\nA replication cluster can easily be setup with the Bitnami Valkey Docker Image using the following environment variables:\n\n- `VALKEY_REPLICATION_MODE`: The replication mode. Possible values `primary`/`replica`. No defaults.\n- `VALKEY_REPLICA_IP`: The replication announce ip. Defaults to `$(get_machine_ip)` which return the ip of the container.\n- `VALKEY_REPLICA_PORT`: The replication announce port. Defaults to `VALKEY_PRIMARY_PORT_NUMBER`.\n- `VALKEY_PRIMARY_HOST`: Hostname/IP of replication primary (replica node parameter). No defaults.\n- `VALKEY_PRIMARY_PORT_NUMBER`: Server port of the replication primary (replica node parameter). Defaults to `6379`.\n- `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.\n\nIn 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.\n\n### Securing Valkey traffic\n\nValkey 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:\n\n- `VALKEY_TLS_ENABLED`: Whether to enable TLS for traffic or not. Defaults to `no`.\n- `VALKEY_TLS_PORT_NUMBER`: Port used for TLS secure traffic. Defaults to `6379`.\n- `VALKEY_TLS_CERT_FILE`: File containing the certificate file for the TLS traffic. No defaults.\n- `VALKEY_TLS_KEY_FILE`: File containing the key for certificate. No defaults.\n- `VALKEY_TLS_CA_FILE`: File containing the CA of the certificate (takes precedence over `VALKEY_TLS_CA_DIR`). No defaults.\n- `VALKEY_TLS_CA_DIR`: Directory containing the CA certificates. No defaults.\n- `VALKEY_TLS_DH_PARAMS_FILE`: File containing DH params (in order to support DH based ciphers). No defaults.\n- `VALKEY_TLS_AUTH_CLIENTS`: Whether to require clients to authenticate or not. Defaults to `yes`.\n\nWhen 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`.\n\nAlternatively, you may also provide with this configuration in your [custom](https://github.com/bitnami/containers/blob/main/bitnami/valkey#configuration-file) configuration file.\n\n### Configuration file\n\nThe 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.\n\n```console\ndocker run --name valkey \\\n -e ALLOW_EMPTY_PASSWORD=yes \\\n -v /path/to/your_valkey.conf:/opt/bitnami/valkey/mounted-etc/valkey.conf \\\n -v /path/to/valkey-data-persistence:/bitnami/valkey/data \\\n REGISTRY_NAME/bitnami/valkey:latest\n```\n\n### Overriding configuration\n\nInstead 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.\n\n```console\ndocker run --name valkey \\\n -e ALLOW_EMPTY_PASSWORD=yes \\\n -v /path/to/overrides.conf:/opt/bitnami/valkey/mounted-etc/overrides.conf \\\n REGISTRY_NAME/bitnami/valkey:latest\n```\n\n### Enable Valkey RDB persistence\n\nWhen 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.\n\n### FIPS configuration in Bitnami Secure Images\n\nThe Bitnami Valkey Docker image from the [Bitnami Secure Images](https://go-vmware.broadcom.com/contact-us) catalog includes extra features and settings to configure the container with FIPS capabilities. You can configure the next environment variables:\n\n- `OPENSSL_FIPS`: whether OpenSSL runs in FIPS mode or not. `yes` (default), `no`.\n\n## Logging\n\nThe Bitnami Valkey 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.\n\n## Notable Changes\n\n### Starting October 20, 2024\n\n- 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.\n\n## License\n\nCopyright © 2026 Broadcom. The term \"Broadcom\" refers to Broadcom Inc. and/or its subsidiaries.\n\nLicensed under the Apache License, Version 2.0 (the \"License\");\nyou may not use this file except in compliance with the License.\nYou may obtain a copy of the License at\n\n\n\nUnless required by applicable law or agreed to in writing, software\ndistributed under the License is distributed on an \"AS IS\" BASIS,\nWITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\nSee the License for the specific language governing permissions and\nlimitations under the License.\n","has_starred","hub_user","carrodher","immutable_tags_settings",{"_115":11,"_116":117},"enabled","rules",[118],".*","is_automated","permissions",{"_122":17,"_123":11,"_124":11},"read","write","admin","user","storage_size",9833258632,"isOrg","reponame","tag","canDeleteTags","isHubSbxKitsEnabled","currentTab","","tagAttestations","displaySecurityMetadata","showSbxLogoOverride","routes/_layout.layers.$namespace.$reponame.$tag.(images).($imageUrlDigest)._index",{"_23":24,"_59":-7,"_57":-7,"_58":-7,"_25":140,"_31":32,"_142":-7,"_143":11},{"_27":28,"_29":30,"_31":32,"_33":34,"_35":36,"_37":141,"_39":40,"_41":30,"_42":43,"_44":45,"_46":47,"_48":49,"_50":-5,"_51":40,"_52":53,"_54":17},[],"imageWithLayers","hasPermissionToViewRepoSettings","actionData","errors"]

bitnami/valkey:sha256-b330d587970c5925265a12d367feba4b6cd89078c75ba118ffb70002834c1a7c.metadata