[{"_1":2,"_143":-5,"_144":-5},"loaderData",{"_3":4,"_13":14,"_21":22,"_137":138},"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":17,"_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},"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:fb6d0b966f9c612cb300848824a3843198c5aeb21bab8392fb96865cc180b2d4","full_size",1243375,"id",1200515627,"images",[],"last_updated","2026-06-15T21:17:49.091627Z","last_updater","last_updater_username","bitnamibot508","media_type","application/vnd.vmware.tac.metadata.config.v1+json","name","sha256-844d41480d41df692d7a916f5be12b2afc28cd784079f1ef8c98321e3d476d76.metadata","repository",24039011,"tag_last_pulled","tag_last_pushed","tag_status","inactive","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":105,"_106":-5,"_107":101,"_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:46:13.559401Z","description","Bitnami Secure Image for valkey-sentinel","is_private","2026-09-03T23:36:44.392716Z","last_modified","2026-03-16T14:23:34.02007Z","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-sentinel","namespace","bitnami","pull_count",826698,"repository_type","star_count",0,"status",1,"status_description","active","source","collaborator_count","full_description","# Bitnami Secure Image for Valkey Sentinel\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 Sentinel](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-sentinel -e VALKEY_PRIMARY_HOST=valkey REGISTRY_NAME/bitnami/valkey-sentinel:latest\n```\n\n**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](#environment-variables) section for a more secure deployment.\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 recommended way to get the Bitnami Valkey Sentinel Docker Image is to pull the prebuilt image from the [Docker Hub Registry](https://hub.docker.com/r/bitnami/valkey-sentinel).\n\n```console\ndocker pull REGISTRY_NAME/bitnami/valkey-sentinel:latest\n```\n\nTo use a specific version, you can pull a versioned tag. You can view the [list of available versions](https://hub.docker.com/r/bitnami/valkey-sentinel/tags/) in the Docker Hub Registry.\n\n```console\ndocker pull REGISTRY_NAME/bitnami/valkey-sentinel:[TAG]\n```\n\nIf 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.\n\n```console\ngit clone https://github.com/bitnami/containers.git\ncd bitnami/APP/VERSION/OPERATING-SYSTEM\ndocker build -t REGISTRY_NAME/bitnami/APP:latest .\n```\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### Using the Command Line\n\nIn this example, we will create a Valkey Sentinel instance that will monitor a Valkey instance that is running on the same docker network.\n\n#### Step 1: Create a network\n\n```console\ndocker network create app-tier --driver bridge\n```\n\n#### Step 2: Launch the Valkey instance\n\nUse the `--network app-tier` argument to the `docker run` command to attach the Valkey container to the `app-tier` network.\n\n```console\ndocker run -d --name valkey-server \\\n -e ALLOW_EMPTY_PASSWORD=yes \\\n --network app-tier \\\n REGISTRY_NAME/bitnami/valkey:latest\n```\n\n#### Step 3: Launch your Valkey Sentinel instance\n\nFinally we create a new container instance to launch the Valkey client and connect to the server created in the previous step:\n\n```console\ndocker run -it --rm \\\n -e VALKEY_PRIMARY_HOST=valkey-server \\\n --network app-tier \\\n REGISTRY_NAME/bitnami/valkey-sentinel:latest\n```\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_SENTINEL_DATA_DIR` | Valkey data directory | `${VALKEY_SENTINEL_VOLUME_DIR}/data` |\n| `VALKEY_SENTINEL_DISABLE_COMMANDS` | Commands to disable in Valkey | `nil` |\n| `VALKEY_SENTINEL_DATABASE` | Default Valkey database | `valkey` |\n| `VALKEY_SENTINEL_AOF_ENABLED` | Enable AOF | `yes` |\n| `VALKEY_SENTINEL_HOST` | Valkey Sentinel host | `nil` |\n| `VALKEY_SENTINEL_PRIMARY_NAME` | Valkey Sentinel primary name | `nil` |\n| `VALKEY_SENTINEL_PORT_NUMBER` | Valkey Sentinel host port | `$VALKEY_SENTINEL_DEFAULT_PORT_NUMBER` |\n| `VALKEY_SENTINEL_QUORUM` | Minimum number of sentinel nodes in order to reach a failover decision | `2` |\n| `VALKEY_SENTINEL_DOWN_AFTER_MILLISECONDS` | Time (in milliseconds) to consider a node to be down | `60000` |\n| `VALKEY_SENTINEL_FAILOVER_TIMEOUT` | Specifies the failover timeout (in milliseconds) | `180000` |\n| `VALKEY_SENTINEL_PRIMARY_REBOOT_DOWN_AFTER_PERIOD` | Specifies the timeout (in milliseconds) for rebooting a primary | `0` |\n| `VALKEY_SENTINEL_RESOLVE_HOSTNAMES` | Enables hostnames support | `yes` |\n| `VALKEY_SENTINEL_ANNOUNCE_HOSTNAMES` | Announce hostnames | `no` |\n| `ALLOW_EMPTY_PASSWORD` | Allow password-less access | `no` |\n| `VALKEY_SENTINEL_PASSWORD` | Password for Valkey | `nil` |\n| `VALKEY_PRIMARY_USER` | Valkey primary node username | `nil` |\n| `VALKEY_PRIMARY_PASSWORD` | Valkey primary node password | `nil` |\n| `VALKEY_SENTINEL_ANNOUNCE_IP` | IP address used to gossip its presence | `nil` |\n| `VALKEY_SENTINEL_ANNOUNCE_PORT` | Port used to gossip its presence | `nil` |\n| `VALKEY_SENTINEL_TLS_ENABLED` | Enable TLS for Valkey authentication | `no` |\n| `VALKEY_SENTINEL_TLS_PORT_NUMBER` | Valkey TLS port (requires VALKEY_SENTINEL_ENABLE_TLS=yes) | `26379` |\n| `VALKEY_SENTINEL_TLS_CERT_FILE` | Valkey TLS certificate file | `nil` |\n| `VALKEY_SENTINEL_TLS_KEY_FILE` | Valkey TLS key file | `nil` |\n| `VALKEY_SENTINEL_TLS_CA_FILE` | Valkey TLS CA file | `nil` |\n| `VALKEY_SENTINEL_TLS_DH_PARAMS_FILE` | Valkey TLS DH parameter file | `nil` |\n| `VALKEY_SENTINEL_TLS_AUTH_CLIENTS` | Enable Valkey TLS client authentication | `yes` |\n| `VALKEY_PRIMARY_HOST` | Valkey primary host (used by replicas) | `valkey` |\n| `VALKEY_PRIMARY_PORT_NUMBER` | Valkey primary host port (used by replicas) | `6379` |\n| `VALKEY_PRIMARY_SET` | Valkey sentinel primary set | `myprimary` |\n\n#### Read-only environment variables\n\n| Name | Description | Value |\n|---------------------------------------|----------------------------------------|--------------------------------------------------|\n| `VALKEY_SENTINEL_VOLUME_DIR` | Persistence base directory | `/bitnami/valkey-sentinel` |\n| `VALKEY_SENTINEL_BASE_DIR` | Valkey installation directory | `${BITNAMI_ROOT_DIR}/valkey-sentinel` |\n| `VALKEY_SENTINEL_CONF_DIR` | Valkey configuration directory | `${VALKEY_SENTINEL_BASE_DIR}/etc` |\n| `VALKEY_SENTINEL_DEFAULT_CONF_DIR` | Valkey default configuration directory | `${VALKEY_SENTINEL_BASE_DIR}/etc.default` |\n| `VALKEY_SENTINEL_MOUNTED_CONF_DIR` | Valkey mounted configuration directory | `${VALKEY_SENTINEL_BASE_DIR}/mounted-etc` |\n| `VALKEY_SENTINEL_CONF_FILE` | Valkey configuration file | `${VALKEY_SENTINEL_CONF_DIR}/sentinel.conf` |\n| `VALKEY_SENTINEL_LOG_DIR` | Valkey logs directory | `${VALKEY_SENTINEL_BASE_DIR}/logs` |\n| `VALKEY_SENTINEL_TMP_DIR` | Valkey temporary directory | `${VALKEY_SENTINEL_BASE_DIR}/tmp` |\n| `VALKEY_SENTINEL_PID_FILE` | Valkey PID file | `${VALKEY_SENTINEL_TMP_DIR}/valkey-sentinel.pid` |\n| `VALKEY_SENTINEL_BIN_DIR` | Valkey executables directory | `${VALKEY_SENTINEL_BASE_DIR}/bin` |\n| `VALKEY_SENTINEL_DAEMON_USER` | Valkey system user | `valkey` |\n| `VALKEY_SENTINEL_DAEMON_GROUP` | Valkey system group | `valkey` |\n| `VALKEY_SENTINEL_DEFAULT_PORT_NUMBER` | Valkey Sentinel host port | `26379` |\n\n### Securing Valkey Sentinel traffic\n\nValkey 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.\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_SENTINEL_PORT_NUMBER` to another port different than `0`.\n\n1. Using `docker run`\n\n ```console\n $ docker run --name valkey-sentinel \\\n -v /path/to/certs:/opt/bitnami/valkey/certs \\\n -v /path/to/valkey-sentinel/persistence:/bitnami \\\n -e VALKEY_PRIMARY_HOST=valkey \\\n -e VALKEY_SENTINEL_TLS_ENABLED=yes \\\n -e VALKEY_SENTINEL_TLS_CERT_FILE=/opt/bitnami/valkey/certs/valkey.crt \\\n -e VALKEY_SENTINEL_TLS_KEY_FILE=/opt/bitnami/valkey/certs/valkey.key \\\n -e VALKEY_SENTINEL_TLS_CA_FILE=/opt/bitnami/valkey/certs/valkeyCA.crt \\\n REGISTRY_NAME/bitnami/valkey-cluster:latest\n REGISTRY_NAME/bitnami/valkey-sentinel:latest\n ```\n\nAlternatively, you may also provide with this configuration in your [custom](https://github.com/bitnami/containers/blob/main/bitnami/valkey-sentinel#configuration-file) configuration file.\n\n### Configuration file\n\nThe 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.\n\n#### Step 1: Run the Valkey Sentinel image\n\nRun the Valkey Sentinel image, mounting a directory from your host.\n\n```console\ndocker run --name valkey-sentinel \\\n -e VALKEY_PRIMARY_HOST=valkey \\\n -v /path/to/valkey-sentinel/persistence:/bitnami \\\n REGISTRY_NAME/bitnami/valkey-sentinel:latest\n```\n\n#### Step 2: Edit the configuration\n\nEdit the configuration on your host using your favorite editor.\n\n```console\nvi /path/to/valkey-persistence/valkey-sentinel/conf/valkey.conf\n```\n\n#### Step 3: Restart Valkey\n\nAfter changing the configuration, restart your Valkey container for changes to take effect.\n\n```console\ndocker restart valkey\n```\n\n### FIPS configuration in Bitnami Secure Images\n\nThe Bitnami Valkey Sentinel 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 Sentinel Docker Image sends the container logs to the `stdout`. To view the logs:\n\n```console\ndocker logs valkey\n```\n\nYou 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",8164748741,"isOrg","reponame","tag","canDeleteTags","isHubSbxKitsEnabled","currentTab","","tagAttestations","displaySecurityMetadata","routes/_layout.layers.$namespace.$reponame.$tag.(images).($imageUrlDigest)._index",{"_23":24,"_59":-7,"_57":-7,"_58":-7,"_25":139,"_31":32,"_141":-7,"_142":11},{"_27":28,"_29":30,"_31":32,"_33":34,"_35":36,"_37":140,"_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-sentinel:sha256-844d41480d41df692d7a916f5be12b2afc28cd784079f1ef8c98321e3d476d76.metadata