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/charts-syncer] Release charts-syncer-2.0.2-debian-12-r4 (#75373)

Browse Source 
Signed-off-by: Bitnami Bot <bitnami-bot@vmware.com>
This commit is contained in:
Bitnami Bot
2024-12-03 22:32:05 +01:00
committed by GitHub
parent e61c3f7841
commit adcd3d8cac
3 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
bitnami/charts-syncer/2/debian-12/Dockerfile
View File

@@ -15,7 +15,7 @@ SHELL ["/bin/bash", "-o", "errexit", "-o", "nounset", "-o", "pipefail", "-c"]
RUN install_packages ca-certificates curl
RUN mkdir -p /tmp/bitnami/pkg/cache/ ; cd /tmp/bitnami/pkg/cache/ ; \
COMPONENTS=( \
"charts-syncer-2.0.2-3-linux-${OS_ARCH}-debian-12" \
"charts-syncer-2.0.2-4-linux-${OS_ARCH}-debian-12" \
) ; \
for COMPONENT in "${COMPONENTS[@]}"; do \
if [ ! -f "${COMPONENT}.tar.gz" ]; then \
@@ -38,10 +38,10 @@ ENV OS_ARCH="${TARGETARCH:-amd64}"
LABEL com.vmware.cp.artifact.flavor="sha256:c50c90cfd9d12b445b011e6ad529f1ad3daea45c26d20b00732fae3cd71f6a83" \
org.opencontainers.image.base.name="scratch" \
org.opencontainers.image.created="2024-11-07T02:32:14Z" \
org.opencontainers.image.created="2024-12-03T20:02:52Z" \
org.opencontainers.image.description="Application packaged by Broadcom, Inc." \
org.opencontainers.image.licenses="Apache-2.0" \
org.opencontainers.image.ref.name="2.0.2-debian-12-r3" \
org.opencontainers.image.ref.name="2.0.2-debian-12-r4" \
org.opencontainers.image.title="charts-syncer" \
org.opencontainers.image.vendor="Broadcom, Inc." \
org.opencontainers.image.version="2.0.2"

2
bitnami/charts-syncer/2/debian-12/prebuildfs/opt/bitnami/.bitnami_components.json
View File

@@ -3,6 +3,6 @@
"arch": "amd64",
"distro": "debian-12",
"type": "NAMI",
"version": "2.0.2-3"
"version": "2.0.2-4"
}
}

4
bitnami/charts-syncer/README.md
View File

@@ -26,11 +26,11 @@ Looking to use charts-syncer in production? Try [VMware Tanzu Application Catalo
## 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`.