[bitnami/redis-sentinel] Release 7.0.8-debian-11-r12 (#24375)

Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>

bitnami/redis-sentinel/7.0/debian-11/Dockerfile

@@ -2,11 +2,11 @@ FROM docker.io/bitnami/minideb:bullseye
 
 ARG TARGETARCH
 
-LABEL org.opencontainers.image.authors="https://bitnami.com/contact" \
-      org.opencontainers.image.description="Application packaged by Bitnami" \
+LABEL org.opencontainers.image.base.name="docker.io/bitnami/minideb:bullseye" \
+      org.opencontainers.image.created="2023-02-17T17:52:20Z" \
+      org.opencontainers.image.description="Application packaged by VMware, Inc" \
       org.opencontainers.image.licenses="Apache-2.0" \
-      org.opencontainers.image.ref.name="7.0.8-debian-11-r11" \
-      org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/redis-sentinel" \
+      org.opencontainers.image.ref.name="7.0.8-debian-11-r12" \
       org.opencontainers.image.title="redis-sentinel" \
       org.opencontainers.image.vendor="VMware, Inc." \
       org.opencontainers.image.version="7.0.8"
@@ -23,8 +23,8 @@ SHELL ["/bin/bash", "-o", "pipefail", "-c"]
 RUN install_packages ca-certificates curl libssl1.1 procps
 RUN mkdir -p /tmp/bitnami/pkg/cache/ && cd /tmp/bitnami/pkg/cache/ && \
     COMPONENTS=( \
-      "redis-sentinel-7.0.8-1-linux-${OS_ARCH}-debian-11" \
-      "gosu-1.16.0-1-linux-${OS_ARCH}-debian-11" \
+      "redis-sentinel-7.0.8-2-linux-${OS_ARCH}-debian-11" \
+      "gosu-1.16.0-2-linux-${OS_ARCH}-debian-11" \
     ) && \
     for COMPONENT in "${COMPONENTS[@]}"; do \
       if [ ! -f "${COMPONENT}.tar.gz" ]; then \

bitnami/redis-sentinel/7.0/debian-11/prebuildfs/opt/bitnami/.bitnami_components.json

@@ -1,16 +1,16 @@
 {
     "gosu": {
         "arch": "amd64",
-        "digest": "9ab9654690d90d3c49ff66fb1eb286487e318adc899d036bc45922f6b176865b",
+        "digest": "f6056076afb745fd7d9d87d20f71e7248d63330352cf5ae0be2130b7f44a8cfa",
         "distro": "debian-11",
         "type": "NAMI",
-        "version": "1.16.0-1"
+        "version": "1.16.0-2"
     },
     "redis-sentinel": {
         "arch": "amd64",
-        "digest": "fa649a98ae84715efbeb60f58d1c3db8888747d4c2ef97ac4b03ec01146b406b",
+        "digest": "48dea779fb0460ac8278cd6412f52f0946b6f86fe137a1eab217f26e77e2bdce",
         "distro": "debian-11",
         "type": "NAMI",
-        "version": "7.0.8-1"
+        "version": "7.0.8-2"
     }
 }

bitnami/redis-sentinel/README.md

@@ -104,7 +104,7 @@ docker run -it --rm \
     bitnami/redis-sentinel:latest
 ```
 
-### Using Docker Compose
+### Using a Docker Compose file
 
 When not specified, Docker Compose automatically sets up a new network and attaches all deployed services to that network. However, we will explicitly define a new `bridge` network named `app-tier`. In this example we assume that you want to connect to the Redis(R) server from your own custom application image which is identified in the following snippet by the service name `myapp`.
 
@@ -227,7 +227,7 @@ When enabling TLS, conventional standard traffic is disabled by default. However
 1. Using `docker run`
 
     ```console
-    docker run --name redis-sentinel \
+    $ docker run --name redis-sentinel \
         -v /path/to/certs:/opt/bitnami/redis/certs \
         -v /path/to/redis-sentinel/persistence:/bitnami \
         -e REDIS_MASTER_HOST=redis \