[{"_1":2,"_142":-5,"_143":-5},"loaderData",{"_3":4,"_13":14,"_20":21,"_136":137},"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},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","routes/_layout.layers.$namespace.$reponame.$tag.(images).($imageUrlDigest)",{"_22":23,"_24":25,"_54":55,"_56":-7,"_57":-7,"_58":-7,"_59":-7,"_60":-5,"_61":-5,"_62":11,"_63":11,"_47":64,"_127":17,"_94":95,"_128":93,"_129":46,"_30":31,"_130":11,"_131":17,"_132":133,"_134":-5,"_135":11},"scanningType","none","tagData",{"_26":27,"_28":29,"_30":31,"_32":33,"_34":35,"_36":37,"_38":39,"_40":29,"_41":42,"_43":44,"_45":46,"_47":48,"_49":-5,"_50":39,"_51":52,"_53":17},"content_type","unrecognized","creator",35095401,"digest","sha256:a8a73ef959f374a01aed4228822b844c3b65949cd8b33b60965ec392c5292c1c","full_size",1252395,"id",1269880717,"images",[],"last_updated","2026-08-14T03:56:14.692443Z","last_updater","last_updater_username","bitnamibot508","media_type","application/vnd.vmware.tac.metadata.config.v1+json","name","sha256-061a40d93f0deb5f390866b0800f96a58dea8adde319af872523f1038b4a3a2b.metadata","repository",229036,"tag_last_pulled","tag_last_pushed","tag_status","inactive","v2","tagImages",[],"layerOrdinals","packageName","cveId","sbom","scoutSummary","staticSummary","isScoutPaymentRequired","canSeeVulnerabilities",{"_65":66,"_77":78,"_80":81,"_82":83,"_84":11,"_38":85,"_86":87,"_88":89,"_45":93,"_94":95,"_96":97,"_98":79,"_99":100,"_101":102,"_103":104,"_105":-5,"_106":107,"_108":109,"_110":11,"_111":95,"_112":113,"_118":17,"_119":120,"_124":95,"_125":126},"categories",[67,71,74],{"_45":68,"_69":70},"Message queues","slug","message-queues",{"_45":72,"_69":73},"Databases & storage","databases-and-storage",{"_45":75,"_69":76},"Monitoring & observability","monitoring-and-observability","content_types",[79,27],"image","date_registered","2015-06-16T00:39:13.718406Z","description","Bitnami Secure Image for redis","is_private","2026-09-03T20:32:47.377482Z","last_modified","2026-03-16T14:23:29.880625Z","media_types",[90,91,92,44],"application/vnd.docker.distribution.manifest.list.v2+json","application/vnd.oci.image.config.v1+json","application/vnd.oci.image.index.v1+json","redis","namespace","bitnami","pull_count",3343976492,"repository_type","star_count",367,"status",1,"status_description","active","source","collaborator_count",0,"full_description","# Bitnami Secure Image for Redis®\n\n> Redis® is an open source, advanced key-value store. It is often referred to as a data structure server since keys can contain strings, hashes, lists, sets and sorted sets.\n\n[Overview of Redis®](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 -e ALLOW_EMPTY_PASSWORD=yes REGISTRY_NAME/bitnami/redis:latest\n```\n\n**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](#configuration) section for a more secure deployment.\n\n## How to deploy Redis(R) 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 Redis(R) Chart GitHub repository](https://github.com/bitnami/charts/tree/master/bitnami/redis).\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) Docker Image is to pull the prebuilt image from the [Docker Hub Registry](https://hub.docker.com/r/bitnami/redis).\n\n```console\ndocker pull REGISTRY_NAME/bitnami/redis: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/tags/) in the Docker Hub Registry.\n\n```console\ndocker pull REGISTRY_NAME/bitnami/redis:[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## Using `docker-compose.yaml`\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/redis).\n\n## Persisting your database\n\nRedis(R) provides a different range of [persistence options](https://redis.io/topics/persistence). 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/redis/run.sh --appendonly no`. Alternatively, you may use the `REDIS_AOF_ENABLED` env variable as explained in [Disabling AOF persistence](https://github.com/bitnami/containers/blob/main/bitnami/redis#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 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## 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_DATA_DIR` | Redis data directory | `${REDIS_VOLUME_DIR}/data` |\n| `REDIS_OVERRIDES_FILE` | Redis config overrides file | `${REDIS_MOUNTED_CONF_DIR}/overrides.conf` |\n| `REDIS_DISABLE_COMMANDS` | Commands to disable in Redis | `nil` |\n| `REDIS_DATABASE` | Default Redis database | `redis` |\n| `REDIS_AOF_ENABLED` | Enable AOF | `yes` |\n| `REDIS_RDB_POLICY` | Enable RDB policy persistence | `nil` |\n| `REDIS_RDB_POLICY_DISABLED` | Allows to enable RDB policy persistence | `no` |\n| `REDIS_MASTER_HOST` | Redis master host (used by slaves) | `nil` |\n| `REDIS_MASTER_PORT_NUMBER` | Redis master host port (used by slaves) | `6379` |\n| `REDIS_PORT_NUMBER` | Redis port number | `$REDIS_DEFAULT_PORT_NUMBER` |\n| `REDIS_ALLOW_REMOTE_CONNECTIONS` | Allow remote connection to the service | `yes` |\n| `REDIS_REPLICATION_MODE` | Redis replication mode (values: master, slave) | `nil` |\n| `REDIS_REPLICA_IP` | The replication announce ip | `nil` |\n| `REDIS_REPLICA_PORT` | The replication announce port | `nil` |\n| `REDIS_EXTRA_FLAGS` | Additional flags pass to 'redis-server' commands | `nil` |\n| `ALLOW_EMPTY_PASSWORD` | Allow password-less access | `no` |\n| `REDIS_PASSWORD` | Password for Redis | `nil` |\n| `REDIS_MASTER_PASSWORD` | Redis master node password | `nil` |\n| `REDIS_ACLFILE` | Redis ACL file | `nil` |\n| `REDIS_IO_THREADS_DO_READS` | Enable multithreading when reading socket | `nil` |\n| `REDIS_IO_THREADS` | Number of threads | `nil` |\n| `REDIS_TLS_ENABLED` | Enable TLS | `no` |\n| `REDIS_TLS_PORT_NUMBER` | Redis TLS port (requires REDIS_ENABLE_TLS=yes) | `6379` |\n| `REDIS_TLS_CERT_FILE` | Redis TLS certificate file | `nil` |\n| `REDIS_TLS_CA_DIR` | Directory containing TLS CA certificates | `nil` |\n| `REDIS_TLS_KEY_FILE` | Redis TLS key file | `nil` |\n| `REDIS_TLS_KEY_FILE_PASS` | Redis TLS key file passphrase | `nil` |\n| `REDIS_TLS_CA_FILE` | Redis TLS CA file | `nil` |\n| `REDIS_TLS_DH_PARAMS_FILE` | Redis TLS DH parameter file | `nil` |\n| `REDIS_TLS_AUTH_CLIENTS` | Enable Redis TLS client authentication | `yes` |\n| `REDIS_SENTINEL_MASTER_NAME` | Redis Sentinel master name | `nil` |\n| `REDIS_SENTINEL_HOST` | Redis Sentinel host | `nil` |\n| `REDIS_SENTINEL_PORT_NUMBER` | Redis Sentinel host port (used by slaves) | `26379` |\n\n#### Read-only environment variables\n\n| Name | Description | Value |\n|-----------------------------|---------------------------------------|---------------------------------|\n| `REDIS_VOLUME_DIR` | Persistence base directory | `/bitnami/redis` |\n| `REDIS_BASE_DIR` | Redis installation directory | `${BITNAMI_ROOT_DIR}/redis` |\n| `REDIS_CONF_DIR` | Redis configuration directory | `${REDIS_BASE_DIR}/etc` |\n| `REDIS_DEFAULT_CONF_DIR` | Redis default configuration directory | `${REDIS_BASE_DIR}/etc.default` |\n| `REDIS_MOUNTED_CONF_DIR` | Redis mounted configuration directory | `${REDIS_BASE_DIR}/mounted-etc` |\n| `REDIS_CONF_FILE` | Redis configuration file | `${REDIS_CONF_DIR}/redis.conf` |\n| `REDIS_LOG_DIR` | Redis logs directory | `${REDIS_BASE_DIR}/logs` |\n| `REDIS_LOG_FILE` | Redis log file | `${REDIS_LOG_DIR}/redis.log` |\n| `REDIS_TMP_DIR` | Redis temporary directory | `${REDIS_BASE_DIR}/tmp` |\n| `REDIS_PID_FILE` | Redis PID file | `${REDIS_TMP_DIR}/redis.pid` |\n| `REDIS_BIN_DIR` | Redis executables directory | `${REDIS_BASE_DIR}/bin` |\n| `REDIS_DAEMON_USER` | Redis system user | `redis` |\n| `REDIS_DAEMON_GROUP` | Redis system group | `redis` |\n| `REDIS_DEFAULT_PORT_NUMBER` | Redis port number (Build time) | `6379` |\n\n### Disabling Redis(R) 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- `REDIS_DISABLE_COMMANDS`: Comma-separated list of Redis(R) commands to disable. Defaults to empty.\n\n### Passing extra command-line flags to redis-server startup\n\nPassing extra command-line flags to the redis service command is possible by adding them as arguments to *run.sh* script:\n\n```console\ndocker run --name redis -e ALLOW_EMPTY_PASSWORD=yes REGISTRY_NAME/bitnami/redis:latest /opt/bitnami/scripts/redis/run.sh --maxmemory 100mb\n```\n\nAlternatively, modify the [`docker-compose.yml`](https://github.com/bitnami/containers/blob/main/bitnami/redis/docker-compose.yml) file present in this repository:\n\n```yaml\nservices:\n redis:\n ...\n environment:\n - ALLOW_EMPTY_PASSWORD=yes\n command: /opt/bitnami/scripts/redis/run.sh --maxmemory 100mb\n ...\n```\n\nRefer to the [Redis(R) documentation](https://redis.io/topics/config#passing-arguments-via-the-command-line) for the complete list of arguments.\n\n### Setting the server password on first run\n\nPassing the `REDIS_PASSWORD` environment variable when running the image for the first time will set the Redis(R) server password to the value of `REDIS_PASSWORD` (or the content of the file specified in `REDIS_PASSWORD_FILE`).\n\n**NOTE**: The at sign (`@`) is not supported for `REDIS_PASSWORD`.\n\n**Warning** The Redis(R) database is always configured with remote access enabled. It's suggested that the `REDIS_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 Redis(R) 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 `REDIS_PASSWORD` for any other scenario.\n\n### Enabling/Setting multithreading\n\nRedis 6.0 features a [new multi-threading model](https://segmentfault.com/a/1190000040376111/en). You can set both `io-threads` and `io-threads-do-reads` though the env vars `REDIS_IO_THREADS` and `REDIS_IO_THREADS_DO_READS`\n\n### Disabling AOF persistence\n\nRedis(R) offers different [options](https://redis.io/topics/persistence) 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 `REDIS_AOF_ENABLED=no` env variable will disable this feature.\n\n### Enabling Access Control List\n\nRedis(R) offers [ACL](https://redis.io/topics/acl) since 6.0 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 `REDIS_ACLFILE`.\n\n```console\ndocker run -name redis -e REDIS_ACLFILE=/opt/bitnami/redis/mounted-etc/users.acl -v /path/to/users.acl:/opt/bitnami/redis/mounted-etc/users.acl REGISTRY_NAME/bitnami/redis:latest\n```\n\nAlternatively, modify the [`docker-compose.yml`](https://github.com/bitnami/containers/blob/main/bitnami/redis/docker-compose.yml) file present in this repository:\n\n```yaml\nservices:\n redis:\n ...\n environment:\n - REDIS_ACLFILE=/opt/bitnami/redis/mounted-etc/users.acl\n volumes:\n - /path/to/users.acl:/opt/bitnami/redis/mounted-etc/users.acl\n ...\n```\n\n### Setting up replication\n\nA [replication](https://redis.io/topics/replication) cluster can easily be setup with the Bitnami Redis(R) Docker Image using the following environment variables:\n\n- `REDIS_REPLICATION_MODE`: The replication mode. Possible values `master`/`slave`. No defaults.\n- `REDIS_REPLICA_IP`: The replication announce ip. Defaults to `$(get_machine_ip)` which return the ip of the container.\n- `REDIS_REPLICA_PORT`: The replication announce port. Defaults to `REDIS_MASTER_PORT_NUMBER`.\n- `REDIS_MASTER_HOST`: Hostname/IP of replication master (replica node parameter). No defaults.\n- `REDIS_MASTER_PORT_NUMBER`: Server port of the replication master (replica node parameter). Defaults to `6379`.\n- `REDIS_MASTER_PASSWORD`: Password to authenticate with the master (replica node parameter). No defaults. As an alternative, you can mount a file with the password and set the `REDIS_MASTER_PASSWORD_FILE` variable.\n\nIn a replication cluster you can have one master and zero or more replicas. When replication is enabled the master 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 Redis(R) 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 following environment variables to configure the application:\n\n- `REDIS_TLS_ENABLED`: Whether to enable TLS for traffic or not. Defaults to `no`.\n- `REDIS_TLS_PORT_NUMBER`: Port used for TLS secure traffic. Defaults to `6379`.\n- `REDIS_TLS_CERT_FILE`: File containing the certificate file for the TLS traffic. No defaults.\n- `REDIS_TLS_KEY_FILE`: File containing the key for certificate. No defaults.\n- `REDIS_TLS_CA_FILE`: File containing the CA of the certificate (takes precedence over `REDIS_TLS_CA_DIR`). No defaults.\n- `REDIS_TLS_CA_DIR`: Directory containing the CA certificates. No defaults.\n- `REDIS_TLS_DH_PARAMS_FILE`: File containing DH params (in order to support DH based ciphers). No defaults.\n- `REDIS_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 `REDIS_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/redis#configuration-file) configuration file.\n\n### Configuration file\n\nThe image looks for configurations in `/opt/bitnami/redis/mounted-etc/redis.conf`. You can overwrite the `redis.conf` file using your own custom configuration file.\n\n```console\ndocker run --name redis \\\n -e ALLOW_EMPTY_PASSWORD=yes \\\n -v /path/to/your_redis.conf:/opt/bitnami/redis/mounted-etc/redis.conf \\\n -v /path/to/redis-data-persistence:/bitnami/redis/data \\\n REGISTRY_NAME/bitnami/redis:latest\n```\n\nAlternatively, modify the [`docker-compose.yml`](https://github.com/bitnami/containers/blob/main/bitnami/redis/docker-compose.yml) file present in this repository:\n\n```yaml\nservices:\n redis:\n ...\n volumes:\n - /path/to/your_redis.conf:/opt/bitnami/redis/mounted-etc/redis.conf\n - /path/to/redis-persistence:/bitnami/redis/data\n ...\n```\n\nRefer to the [Redis(R) configuration](https://redis.io/topics/config) manual for the complete list of configuration options.\n\n### Overriding configuration\n\nInstead of providing a custom `redis.conf`, you may also choose to provide only settings you wish to override. The image will look for `/opt/bitnami/redis/mounted-etc/overrides.conf`. This will be ignored if custom `redis.conf` is provided.\n\n```console\ndocker run --name redis \\\n -e ALLOW_EMPTY_PASSWORD=yes \\\n -v /path/to/overrides.conf:/opt/bitnami/redis/mounted-etc/overrides.conf \\\n REGISTRY_NAME/bitnami/redis:latest\n```\n\nAlternatively, modify the [`docker-compose.yml`](https://github.com/bitnami/containers/blob/main/bitnami/redis/docker-compose.yml) file present in this repository:\n\n```yaml\nservices:\n redis:\n ...\n volumes:\n - /path/to/overrides.conf:/opt/bitnami/redis/mounted-etc/overrides.conf\n ...\n```\n\n### Enable Redis(R) RDB persistence\n\nWhen the value of `REDIS_RDB_POLICY_DISABLED` is `no` (default value) the Redis(R) default persistence strategy will be used. If you want to modify the default strategy, you can configure it through the `REDIS_RDB_POLICY` parameter.\n\n### FIPS configuration in Bitnami Secure Images\n\nThe Bitnami Redis® 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) Docker image sends the container logs to the `stdout`. To view the logs:\n\n```console\ndocker logs redis\n```\n\nor using Docker Compose:\n\n```console\ndocker-compose 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### 5.0.8-debian-10-r24\n\n- The recommended mount point to use a custom `redis.conf` changes from `/opt/bitnami/redis/etc/` to `/opt/bitnami/redis/mounted-etc/`.\n\n### 5.0.0-r0\n\n- Starting with Redis(R) 5.0 the command [REPLICAOF](https://redis.io/commands/replicaof) is available in favor of `SLAVEOF`. For backward compatibility with previous versions, `slave` replication mode is still supported. We encourage the use of the `REPLICAOF` command if you are using Redis(R) 5.0.\n\n### 4.0.1-r24\n\n- Decrease the size of the container. It is not necessary Node.js anymore. Redis(R) configuration moved to bash scripts in the `rootfs/` folder.\n- The recommended mount point to persist data changes to `/bitnami/redis/data`.\n- The main `redis.conf` file is not persisted in a volume. The path is `/opt/bitnami/redis/mounted-etc/redis.conf`.\n- Backwards compatibility is not guaranteed when data is persisted using docker-compose. You can use the workaround below to overcome it:\n\n```bash\ndocker-compose down\n## Locate your volume and modify the file tree\nVOLUME=$(docker volume ls | grep \"redis_data\" | awk '{print $2}')\ndocker run --rm -i -v=${VOLUME}:/tmp/redis busybox find /tmp/redis/data -maxdepth 1 -exec mv {} /tmp/redis \\;\ndocker run --rm -i -v=${VOLUME}:/tmp/redis busybox rm -rf /tmp/redis/{data,conf,.initialized}\n## Change the mount point\nsed -i -e 's#redis_data:/bitnami/redis#redis_data:/bitnami/redis/data#g' docker-compose.yml\n## Pull the latest bitnami/redis image\ndocker pull REGISTRY_NAME/bitnami/redis:latest\ndocker-compose up -d\n```\n\n### 4.0.1-r1\n\n- The redis 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`.\n As a consequence, the configuration files are writable by the user running the redis process.\n\n### 3.2.0-r0\n\n- All volumes have been merged at `/bitnami/redis`. Now you only need to mount a single volume at `/bitnami/redis` for persistence.\n- The logs are always sent to the `stdout` and are no longer collected in the volume.\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",{"_114":11,"_115":116},"enabled","rules",[117],".*","is_automated","permissions",{"_121":17,"_122":11,"_123":11},"read","write","admin","user","storage_size",166997965653,"isOrg","reponame","tag","canDeleteTags","isHubSbxKitsEnabled","currentTab","","tagAttestations","displaySecurityMetadata","routes/_layout.layers.$namespace.$reponame.$tag.(images).($imageUrlDigest)._index",{"_22":23,"_58":-7,"_56":-7,"_57":-7,"_24":138,"_30":31,"_140":-7,"_141":11},{"_26":27,"_28":29,"_30":31,"_32":33,"_34":35,"_36":139,"_38":39,"_40":29,"_41":42,"_43":44,"_45":46,"_47":48,"_49":-5,"_50":39,"_51":52,"_53":17},[],"imageWithLayers","hasPermissionToViewRepoSettings","actionData","errors"]

bitnami/redis:sha256-061a40d93f0deb5f390866b0800f96a58dea8adde319af872523f1038b4a3a2b.metadata