Bitnami/containers
2
0
Fork 0
mirror of https://github.com/bitnami/containers.git synced 2026-02-19 22:17:24 +08:00
Code Issues Packages Projects Releases Wiki Activity

[bitnami/hubble-ui-backend] Release hubble-ui-backend-0.13.1-debian-12-r16 (#75423)

Browse Source 
Signed-off-by: Bitnami Bot <bitnami-bot@vmware.com>
This commit is contained in:
Bitnami Bot
2024-12-04 00:48:29 +01:00
committed by GitHub
parent a892119f18
commit 050ad194b7
3 changed files with 8 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
bitnami/hubble-ui-backend/0/debian-12/Dockerfile
View File

@@ -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:16:17Z" \
org.opencontainers.image.created="2024-12-03T23:11:43Z" \
org.opencontainers.image.description="Application packaged by Broadcom, Inc." \
org.opencontainers.image.documentation="https://github.com/bitnami/containers/tree/main/bitnami/hubble-ui-backend/README.md" \
org.opencontainers.image.licenses="Apache-2.0" \
org.opencontainers.image.ref.name="0.13.1-debian-12-r15" \
org.opencontainers.image.ref.name="0.13.1-debian-12-r16" \
org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/hubble-ui-backend" \
org.opencontainers.image.title="hubble-ui-backend" \
org.opencontainers.image.vendor="Broadcom, Inc." \
@@ -29,8 +29,8 @@ SHELL ["/bin/bash", "-o", "errexit", "-o", "nounset", "-o", "pipefail", "-c"]
RUN install_packages ca-certificates curl procps
RUN mkdir -p /tmp/bitnami/pkg/cache/ ; cd /tmp/bitnami/pkg/cache/ ; \
COMPONENTS=( \
"gops-0.3.28-10-linux-${OS_ARCH}-debian-12" \
"hubble-ui-backend-0.13.1-9-linux-${OS_ARCH}-debian-12" \
"gops-0.3.28-11-linux-${OS_ARCH}-debian-12" \
"hubble-ui-backend-0.13.1-10-linux-${OS_ARCH}-debian-12" \
) ; \
for COMPONENT in "${COMPONENTS[@]}"; do \
if [ ! -f "${COMPONENT}.tar.gz" ]; then \

4
bitnami/hubble-ui-backend/0/debian-12/prebuildfs/opt/bitnami/.bitnami_components.json
View File

@@ -3,12 +3,12 @@
"arch": "amd64",
"distro": "debian-12",
"type": "NAMI",
"version": "0.3.28-10"
"version": "0.3.28-11"
},
"hubble-ui-backend": {
"arch": "amd64",
"distro": "debian-12",
"type": "NAMI",
"version": "0.13.1-9"
"version": "0.13.1-10"
}
}

4
bitnami/hubble-ui-backend/README.md
View File

@@ -26,11 +26,11 @@ Looking to use Hubble UI Backend in production? Try [VMware Tanzu Application Ca
## 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`.