From 21861efd45a4bb3b71c84c456fb9e7a156a80ed3 Mon Sep 17 00:00:00 2001 From: Bitnami Bot Date: Mon, 25 Nov 2024 01:58:14 +0100 Subject: [PATCH] [bitnami/consul] Release consul-1.20.1-debian-12-r3 (#75181) Signed-off-by: Bitnami Bot --- bitnami/consul/1/debian-12/Dockerfile | 4 ++-- bitnami/consul/README.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/bitnami/consul/1/debian-12/Dockerfile b/bitnami/consul/1/debian-12/Dockerfile index 81944aded3d5..0b3953605760 100644 --- a/bitnami/consul/1/debian-12/Dockerfile +++ b/bitnami/consul/1/debian-12/Dockerfile @@ -8,11 +8,11 @@ ARG TARGETARCH LABEL com.vmware.cp.artifact.flavor="sha256:c50c90cfd9d12b445b011e6ad529f1ad3daea45c26d20b00732fae3cd71f6a83" \ org.opencontainers.image.base.name="docker.io/bitnami/minideb:bookworm" \ - org.opencontainers.image.created="2024-11-09T18:15:28Z" \ + org.opencontainers.image.created="2024-11-25T00:24:00Z" \ org.opencontainers.image.description="Application packaged by Broadcom, Inc." \ org.opencontainers.image.documentation="https://github.com/bitnami/containers/tree/main/bitnami/consul/README.md" \ org.opencontainers.image.licenses="Apache-2.0" \ - org.opencontainers.image.ref.name="1.20.1-debian-12-r2" \ + org.opencontainers.image.ref.name="1.20.1-debian-12-r3" \ org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/consul" \ org.opencontainers.image.title="consul" \ org.opencontainers.image.vendor="Broadcom, Inc." \ diff --git a/bitnami/consul/README.md b/bitnami/consul/README.md index d472232f4469..21c66e5e1f33 100644 --- a/bitnami/consul/README.md +++ b/bitnami/consul/README.md @@ -34,11 +34,11 @@ Bitnami containers can be used with [Kubeapps](https://kubeapps.dev/) for deploy ## 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.vmware.com/en/VMware-Tanzu-Application-Catalog/services/tutorials/GUID-work-with-non-root-containers-index.html). +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://techdocs.broadcom.com/us/en/vmware-tanzu/application-catalog/tanzu-application-catalog/services/tac-doc/apps-tutorials-work-with-non-root-containers-index.html). ## Supported tags and respective `Dockerfile` links -Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags [in our documentation page](https://docs.vmware.com/en/VMware-Tanzu-Application-Catalog/services/tutorials/GUID-understand-rolling-tags-containers-index.html). +Learn 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). You can see the equivalence between the different tags by taking a look at the `tags-info.yaml` file present in the branch folder, i.e `bitnami/ASSET/BRANCH/DISTRO/tags-info.yaml`.