[{"_1":2,"_136":-5,"_137":-5},"loaderData",{"_3":4,"_13":14,"_19":20,"_130":131},"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},"username","isAskGordonEnabled",true,"isUsingNewTemplate","routes/_layout.layers.$namespace.$reponame.$tag.(images).($imageUrlDigest)",{"_21":22,"_23":24,"_53":54,"_55":-7,"_56":-7,"_57":-7,"_58":-7,"_46":59,"_121":17,"_89":90,"_122":88,"_123":45,"_29":30,"_124":11,"_125":11,"_126":127,"_128":-5,"_129":11},"scanningType","none","tagData",{"_25":26,"_27":28,"_29":30,"_31":32,"_33":34,"_35":36,"_37":38,"_39":28,"_40":41,"_42":43,"_44":45,"_46":47,"_48":-5,"_49":38,"_50":51,"_52":17},"content_type","unrecognized","creator",35095401,"digest","sha256:d291e19261e393d5c6613de923755431d897193fb5e8cef53577e487dc6fc59c","full_size",1194266,"id",1279577584,"images",[],"last_updated","2026-08-22T06:59:34.260451Z","last_updater","last_updater_username","bitnamibot508","media_type","application/vnd.vmware.tac.metadata.config.v1+json","name","sha256-fcfca07d8b56cea8e990e51c09c0d03102bde09a2147bd6a669e024a56893a8c.metadata","repository",5552909,"tag_last_pulled","tag_last_pushed","tag_status","active","v2","tagImages",[],"layerOrdinals","packageName","cveId","sbom",{"_60":61,"_72":73,"_75":76,"_77":78,"_79":11,"_37":80,"_81":82,"_83":84,"_44":88,"_89":90,"_91":92,"_93":74,"_94":95,"_96":97,"_98":51,"_99":-5,"_100":101,"_102":103,"_104":11,"_105":90,"_106":107,"_112":17,"_113":114,"_118":90,"_119":120},"categories",[62,66,69],{"_44":63,"_64":65},"Message queues","slug","message-queues",{"_44":67,"_64":68},"Databases & storage","databases-and-storage",{"_44":70,"_64":71},"Monitoring & observability","monitoring-and-observability","content_types",[74,26],"image","date_registered","2018-05-29T14:44:35.494928Z","description","Bitnami Secure Image for redis-sentinel","is_private","2026-08-22T06:59:39.197429Z","last_modified","2026-03-16T14:23:28.570853Z","media_types",[85,86,87,43],"application/vnd.docker.distribution.manifest.list.v2+json","application/vnd.oci.image.config.v1+json","application/vnd.oci.image.index.v1+json","redis-sentinel","namespace","bitnami","pull_count",183533346,"repository_type","star_count",55,"status",1,"status_description","source","collaborator_count",0,"full_description","# Bitnami Secure Image for Redis® Sentinel\n\n> Redis® Sentinel provides high availability for Redis. Redis Sentinel also provides other collateral tasks such as monitoring, notifications and acts as a configuration provider for clients.\n\n[Overview of Redis® Sentinel](https://redis.io)\nDisclaimer: 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.\n\n## TL;DR\n\n```console\ndocker run --name redis-sentinel -e REDIS_MASTER_HOST=redis REGISTRY_NAME/bitnami/redis-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 Redis(R) Sentinel Docker Image is to pull the prebuilt image from the [Docker Hub Registry](https://hub.docker.com/r/bitnami/redis-sentinel).\n\n```console\ndocker pull REGISTRY_NAME/bitnami/redis-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/redis-sentinel/tags/) in the Docker Hub Registry.\n\n```console\ndocker pull REGISTRY_NAME/bitnami/redis-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 Redis(R) 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 Redis(R) Sentinel instance that will monitor a Redis(R) 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 Redis(R) instance\n\nUse the `--network app-tier` argument to the `docker run` command to attach the Redis(R) container to the `app-tier` network.\n\n```console\ndocker run -d --name redis-server \\\n -e ALLOW_EMPTY_PASSWORD=yes \\\n --network app-tier \\\n REGISTRY_NAME/bitnami/redis:latest\n```\n\n#### Step 3: Launch your Redis(R) Sentinel instance\n\nFinally we create a new container instance to launch the Redis(R) client and connect to the server created in the previous step:\n\n```console\ndocker run -it --rm \\\n -e REDIS_MASTER_HOST=redis-server \\\n --network app-tier \\\n REGISTRY_NAME/bitnami/redis-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| `REDIS_SENTINEL_DATA_DIR` | Redis data directory | `${REDIS_SENTINEL_VOLUME_DIR}/data` |\n| `REDIS_SENTINEL_DISABLE_COMMANDS` | Commands to disable in Redis | `nil` |\n| `REDIS_SENTINEL_DATABASE` | Default Redis database | `redis` |\n| `REDIS_SENTINEL_AOF_ENABLED` | Enable AOF | `yes` |\n| `REDIS_SENTINEL_HOST` | Redis Sentinel host | `nil` |\n| `REDIS_SENTINEL_MASTER_NAME` | Redis Sentinel master name | `nil` |\n| `REDIS_SENTINEL_PORT_NUMBER` | Redis Sentinel host port | `$REDIS_SENTINEL_DEFAULT_PORT_NUMBER` |\n| `REDIS_SENTINEL_QUORUM` | Minimum number of sentinel nodes in order to reach a failover decision | `2` |\n| `REDIS_SENTINEL_DOWN_AFTER_MILLISECONDS` | Time (in milliseconds) to consider a node to be down | `60000` |\n| `REDIS_SENTINEL_FAILOVER_TIMEOUT` | Specifies the failover timeout (in milliseconds) | `180000` |\n| `REDIS_SENTINEL_MASTER_REBOOT_DOWN_AFTER_PERIOD` | Specifies the timeout (in milliseconds) for rebooting a master | `0` |\n| `REDIS_SENTINEL_RESOLVE_HOSTNAMES` | Enables hostnames support | `yes` |\n| `REDIS_SENTINEL_ANNOUNCE_HOSTNAMES` | Announce hostnames | `no` |\n| `ALLOW_EMPTY_PASSWORD` | Allow password-less access | `no` |\n| `REDIS_SENTINEL_PASSWORD` | Password for Redis | `nil` |\n| `REDIS_MASTER_USER` | Redis master node username | `nil` |\n| `REDIS_MASTER_PASSWORD` | Redis master node password | `nil` |\n| `REDIS_SENTINEL_ANNOUNCE_IP` | IP address used to gossip its presence | `nil` |\n| `REDIS_SENTINEL_ANNOUNCE_PORT` | Port used to gossip its presence | `nil` |\n| `REDIS_SENTINEL_TLS_ENABLED` | Enable TLS for Redis authentication | `no` |\n| `REDIS_SENTINEL_TLS_PORT_NUMBER` | Redis TLS port (requires REDIS_SENTINEL_ENABLE_TLS=yes) | `26379` |\n| `REDIS_SENTINEL_TLS_CERT_FILE` | Redis TLS certificate file | `nil` |\n| `REDIS_SENTINEL_TLS_KEY_FILE` | Redis TLS key file | `nil` |\n| `REDIS_SENTINEL_TLS_CA_FILE` | Redis TLS CA file | `nil` |\n| `REDIS_SENTINEL_TLS_CA_DIR` | Directory containing TLS CA certificates | `nil` |\n| `REDIS_SENTINEL_TLS_DH_PARAMS_FILE` | Redis TLS DH parameter file | `nil` |\n| `REDIS_SENTINEL_TLS_AUTH_CLIENTS` | Enable Redis TLS client authentication | `yes` |\n| `REDIS_MASTER_HOST` | Redis master host (used by slaves) | `redis` |\n| `REDIS_MASTER_PORT_NUMBER` | Redis master host port (used by slaves) | `6379` |\n| `REDIS_MASTER_SET` | Redis sentinel master set | `mymaster` |\n\n#### Read-only environment variables\n\n| Name | Description | Value |\n|--------------------------------------|---------------------------------------|------------------------------------------------|\n| `REDIS_SENTINEL_VOLUME_DIR` | Persistence base directory | `/bitnami/redis-sentinel` |\n| `REDIS_SENTINEL_BASE_DIR` | Redis installation directory | `${BITNAMI_ROOT_DIR}/redis-sentinel` |\n| `REDIS_SENTINEL_CONF_DIR` | Redis configuration directory | `${REDIS_SENTINEL_BASE_DIR}/etc` |\n| `REDIS_SENTINEL_DEFAULT_CONF_DIR` | Redis default configuration directory | `${REDIS_SENTINEL_BASE_DIR}/etc.default` |\n| `REDIS_SENTINEL_MOUNTED_CONF_DIR` | Redis mounted configuration directory | `${REDIS_SENTINEL_BASE_DIR}/mounted-etc` |\n| `REDIS_SENTINEL_CONF_FILE` | Redis configuration file | `${REDIS_SENTINEL_CONF_DIR}/sentinel.conf` |\n| `REDIS_SENTINEL_LOG_DIR` | Redis logs directory | `${REDIS_SENTINEL_BASE_DIR}/logs` |\n| `REDIS_SENTINEL_TMP_DIR` | Redis temporary directory | `${REDIS_SENTINEL_BASE_DIR}/tmp` |\n| `REDIS_SENTINEL_PID_FILE` | Redis PID file | `${REDIS_SENTINEL_TMP_DIR}/redis-sentinel.pid` |\n| `REDIS_SENTINEL_BIN_DIR` | Redis executables directory | `${REDIS_SENTINEL_BASE_DIR}/bin` |\n| `REDIS_SENTINEL_DAEMON_USER` | Redis system user | `redis` |\n| `REDIS_SENTINEL_DAEMON_GROUP` | Redis system group | `redis` |\n| `REDIS_SENTINEL_DEFAULT_PORT_NUMBER` | Redis Sentinel host port | `26379` |\n\n### Securing Redis(R) Sentinel traffic\n\nStarting 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.\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 `REDIS_SENTINEL_PORT_NUMBER` to another port different than `0`.\n\n1. Using `docker run`\n\n ```console\n $ docker run --name redis-sentinel \\\n -v /path/to/certs:/opt/bitnami/redis/certs \\\n -v /path/to/redis-sentinel/persistence:/bitnami \\\n -e REDIS_MASTER_HOST=redis \\\n -e REDIS_SENTINEL_TLS_ENABLED=yes \\\n -e REDIS_SENTINEL_TLS_CERT_FILE=/opt/bitnami/redis/certs/redis.crt \\\n -e REDIS_SENTINEL_TLS_KEY_FILE=/opt/bitnami/redis/certs/redis.key \\\n -e REDIS_SENTINEL_TLS_CA_FILE=/opt/bitnami/redis/certs/redisCA.crt \\\n REGISTRY_NAME/bitnami/redis-cluster:latest\n REGISTRY_NAME/bitnami/redis-sentinel:latest\n ```\n\nAlternatively, you may also provide with this configuration in your [custom](https://github.com/bitnami/containers/blob/main/bitnami/redis-sentinel#configuration-file) configuration file.\n\n### Configuration file\n\nThe 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.\n\n#### Step 1: Run the Redis(R) Sentinel image\n\nRun the Redis(R) Sentinel image, mounting a directory from your host.\n\n```console\ndocker run --name redis-sentinel \\\n -e REDIS_MASTER_HOST=redis \\\n -v /path/to/redis-sentinel/persistence:/bitnami \\\n REGISTRY_NAME/bitnami/redis-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/redis-persistence/redis-sentinel/conf/redis.conf\n```\n\n#### Step 3: Restart Redis(R)\n\nAfter changing the configuration, restart your Redis(R) container for changes to take effect.\n\n```console\ndocker restart redis\n```\n\nRefer to the [Redis(R) configuration](https://redis.iotopics/config) manual for the complete list of configuration options.\n\n### FIPS configuration in Bitnami Secure Images\n\nThe Bitnami Redis® 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 Redis(R) Sentinel Docker Image sends the container logs to the `stdout`. To view the logs:\n\n```console\ndocker logs redis\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 January 16, 2024\n\n- The `docker-compose.yaml` file has been removed, as it was solely intended for internal testing purposes.\n\n### 4.0.14-debian-9-r201, 4.0.14-ol-7-r222, 5.0.5-debian-9-r169, 5.0.5-ol-7-r175\n\n- Decrease the size of the container. The configuration logic is now based on Bash scripts in the `rootfs/` folder.\n\n### 4.0.10-r25\n\n- 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.\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","immutable_tags_settings",{"_108":11,"_109":110},"enabled","rules",[111],".*","is_automated","permissions",{"_115":17,"_116":11,"_117":11},"read","write","admin","user","storage_size",145640588972,"isOrg","reponame","tag","canDeleteTags","isHubSbxKitsEnabled","currentTab","","tagAttestations","displaySecurityMetadata","routes/_layout.layers.$namespace.$reponame.$tag.(images).($imageUrlDigest)._index",{"_21":22,"_57":-7,"_55":-7,"_56":-7,"_23":132,"_29":30,"_134":-7,"_135":11},{"_25":26,"_27":28,"_29":30,"_31":32,"_33":34,"_35":133,"_37":38,"_39":28,"_40":41,"_42":43,"_44":45,"_46":47,"_48":-5,"_49":38,"_50":51,"_52":17},[],"imageWithLayers","hasPermissionToViewRepoSettings","actionData","errors"]

Help

System theme

Docker Suite

bitnami/redis-sentinel:sha256-fcfca07d8b56cea8e990e51c09c0d03102bde09a2147bd6a669e024a56893a8c.metadata