[bitnami/configmap-reload] Release 0.8.0-debian-11-r70 (#33460)

Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
This commit is contained in:
Bitnami Bot
2023-05-11 19:28:57 +01:00
committed by GitHub
parent 88fde060df
commit 73ccc955a8
2 changed files with 4 additions and 2 deletions

View File

@@ -3,10 +3,10 @@ FROM docker.io/bitnami/minideb:bullseye
ARG TARGETARCH
LABEL org.opencontainers.image.base.name="docker.io/bitnami/minideb:bullseye" \
org.opencontainers.image.created="2023-05-08T17:55:42Z" \
org.opencontainers.image.created="2023-05-11T18:12:47Z" \
org.opencontainers.image.description="Application packaged by VMware, Inc" \
org.opencontainers.image.licenses="Apache-2.0" \
org.opencontainers.image.ref.name="0.8.0-debian-11-r69" \
org.opencontainers.image.ref.name="0.8.0-debian-11-r70" \
org.opencontainers.image.title="configmap-reload" \
org.opencontainers.image.vendor="VMware, Inc." \
org.opencontainers.image.version="0.8.0"

View File

@@ -20,6 +20,8 @@ Deploy [ConfigMap Reload](https://github.com/jimmidyson/configmap-reload/blob/ma
* All Bitnami images available in Docker Hub are signed with [Docker Content Trust (DCT)](https://docs.docker.com/engine/security/trust/content_trust/). You can use `DOCKER_CONTENT_TRUST=1` to verify the integrity of the images.
* Bitnami container images are released on a regular basis with the latest distribution packages available.
Looking to use ConfigMap Reload in production? Try [VMware Application Catalog](https://bitnami.com/enterprise), the enterprise edition of Bitnami Application Catalog.
## Why use a non-root container?
Non-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://docs.bitnami.com/tutorials/work-with-non-root-containers/).