[bitnami/prometheus-rsocket-proxy] Release 1.5.0-debian-11-r87 (#33572)

Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
This commit is contained in:
Bitnami Bot
2023-05-12 08:13:47 +01:00
committed by GitHub
parent 0756a7e099
commit ffbbf8ae8a
3 changed files with 6 additions and 4 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-09T06:36:57Z" \
org.opencontainers.image.created="2023-05-12T06:51:56Z" \
org.opencontainers.image.description="Application packaged by VMware, Inc" \
org.opencontainers.image.licenses="Apache-2.0" \
org.opencontainers.image.ref.name="1.5.0-debian-11-r86" \
org.opencontainers.image.ref.name="1.5.0-debian-11-r87" \
org.opencontainers.image.title="prometheus-rsocket-proxy" \
org.opencontainers.image.vendor="VMware, Inc." \
org.opencontainers.image.version="1.5.0"
@@ -22,7 +22,7 @@ SHELL ["/bin/bash", "-o", "pipefail", "-c"]
RUN install_packages ca-certificates curl libgcc-s1 procps
RUN mkdir -p /tmp/bitnami/pkg/cache/ && cd /tmp/bitnami/pkg/cache/ && \
COMPONENTS=( \
"java-1.8.362-4-linux-${OS_ARCH}-debian-11" \
"java-1.8.372-7-0-linux-${OS_ARCH}-debian-11" \
"prometheus-rsocket-proxy-1.5.0-8-linux-${OS_ARCH}-debian-11" \
) && \
for COMPONENT in "${COMPONENTS[@]}"; do \

View File

@@ -3,7 +3,7 @@
"arch": "amd64",
"distro": "debian-11",
"type": "NAMI",
"version": "1.8.362-4"
"version": "1.8.372-7-0"
},
"prometheus-rsocket-proxy": {
"arch": "amd64",

View File

@@ -25,6 +25,8 @@ docker-compose up -d
* 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 Prometheus RSocket Proxy 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/).