[bitnami/grafana] Release grafana-10.4.13-debian-12-r0 (#75005)

Signed-off-by: Bitnami Bot <bitnami-bot@vmware.com>
This commit is contained in:
Bitnami Bot
2024-11-19 15:36:19 +01:00
committed by GitHub
parent 8a3cdd1630
commit adb0eed9b3
4 changed files with 9 additions and 9 deletions

View File

@@ -8,15 +8,15 @@ ARG TARGETARCH
LABEL com.vmware.cp.artifact.flavor="sha256:c50c90cfd9d12b445b011e6ad529f1ad3daea45c26d20b00732fae3cd71f6a83" \ LABEL com.vmware.cp.artifact.flavor="sha256:c50c90cfd9d12b445b011e6ad529f1ad3daea45c26d20b00732fae3cd71f6a83" \
org.opencontainers.image.base.name="docker.io/bitnami/minideb:bookworm" \ org.opencontainers.image.base.name="docker.io/bitnami/minideb:bookworm" \
org.opencontainers.image.created="2024-11-10T00:56:28Z" \ org.opencontainers.image.created="2024-11-19T14:12:22Z" \
org.opencontainers.image.description="Application packaged by Broadcom, Inc." \ org.opencontainers.image.description="Application packaged by Broadcom, Inc." \
org.opencontainers.image.documentation="https://github.com/bitnami/containers/tree/main/bitnami/grafana/README.md" \ org.opencontainers.image.documentation="https://github.com/bitnami/containers/tree/main/bitnami/grafana/README.md" \
org.opencontainers.image.licenses="Apache-2.0" \ org.opencontainers.image.licenses="Apache-2.0" \
org.opencontainers.image.ref.name="10.4.11-debian-12-r3" \ org.opencontainers.image.ref.name="10.4.13-debian-12-r0" \
org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/grafana" \ org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/grafana" \
org.opencontainers.image.title="grafana" \ org.opencontainers.image.title="grafana" \
org.opencontainers.image.vendor="Broadcom, Inc." \ org.opencontainers.image.vendor="Broadcom, Inc." \
org.opencontainers.image.version="10.4.11" org.opencontainers.image.version="10.4.13"
ENV HOME="/" \ ENV HOME="/" \
OS_ARCH="${TARGETARCH:-amd64}" \ OS_ARCH="${TARGETARCH:-amd64}" \
@@ -31,7 +31,7 @@ RUN mkdir -p /tmp/bitnami/pkg/cache/ ; cd /tmp/bitnami/pkg/cache/ ; \
COMPONENTS=( \ COMPONENTS=( \
"mysql-client-10.11.10-0-linux-${OS_ARCH}-debian-12" \ "mysql-client-10.11.10-0-linux-${OS_ARCH}-debian-12" \
"ini-file-1.4.7-7-linux-${OS_ARCH}-debian-12" \ "ini-file-1.4.7-7-linux-${OS_ARCH}-debian-12" \
"grafana-10.4.11-3-linux-${OS_ARCH}-debian-12" \ "grafana-10.4.13-0-linux-${OS_ARCH}-debian-12" \
) ; \ ) ; \
for COMPONENT in "${COMPONENTS[@]}"; do \ for COMPONENT in "${COMPONENTS[@]}"; do \
if [ ! -f "${COMPONENT}.tar.gz" ]; then \ if [ ! -f "${COMPONENT}.tar.gz" ]; then \
@@ -49,7 +49,7 @@ RUN find / -perm /6000 -type f -exec chmod a-s {} \; || true
COPY rootfs / COPY rootfs /
RUN /opt/bitnami/scripts/grafana/postunpack.sh RUN /opt/bitnami/scripts/grafana/postunpack.sh
ENV APP_VERSION="10.4.11" \ ENV APP_VERSION="10.4.13" \
BITNAMI_APP_NAME="grafana" \ BITNAMI_APP_NAME="grafana" \
PATH="/opt/bitnami/mysql/bin:/opt/bitnami/common/bin:/opt/bitnami/grafana/bin:$PATH" PATH="/opt/bitnami/mysql/bin:/opt/bitnami/common/bin:/opt/bitnami/grafana/bin:$PATH"

View File

@@ -3,7 +3,7 @@
"arch": "amd64", "arch": "amd64",
"distro": "debian-12", "distro": "debian-12",
"type": "NAMI", "type": "NAMI",
"version": "10.4.11-3" "version": "10.4.13-0"
}, },
"ini-file": { "ini-file": {
"arch": "amd64", "arch": "amd64",

View File

@@ -1,4 +1,4 @@
rolling-tags: rolling-tags:
- "10" - "10"
- 10-debian-12 - 10-debian-12
- 10.4.11 - 10.4.13

View File

@@ -32,11 +32,11 @@ Bitnami containers can be used with [Kubeapps](https://kubeapps.dev/) for deploy
## Why use a non-root container? ## 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 ## 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`. 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`.