Bitnami/containers
2
0
Fork 0
mirror of https://github.com/bitnami/containers.git synced 2026-04-01 06:48:13 +08:00
Code Issues Packages Projects Releases Wiki Activity

[bitnami/cilium] Release cilium-1.16.4-debian-12-r0 (#75010)

Browse Source 
Signed-off-by: Bitnami Bot <bitnami-bot@vmware.com>
This commit is contained in:
Bitnami Bot
2024-11-19 17:28:23 +01:00
committed by GitHub
parent e924635c3a
commit fd4f81351e
4 changed files with 9 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
bitnami/cilium/1/debian-12/Dockerfile
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-09T20:07:40Z" \ org.opencontainers.image.created="2024-11-19T16:05:01Z" \
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/cilium/README.md" \ org.opencontainers.image.documentation="https://github.com/bitnami/containers/tree/main/bitnami/cilium/README.md" \
org.opencontainers.image.licenses="Apache-2.0" \ org.opencontainers.image.licenses="Apache-2.0" \
org.opencontainers.image.ref.name="1.16.3-debian-12-r4" \ org.opencontainers.image.ref.name="1.16.4-debian-12-r0" \
org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/cilium" \ org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/cilium" \
org.opencontainers.image.title="cilium" \ org.opencontainers.image.title="cilium" \
org.opencontainers.image.vendor="Broadcom, Inc." \ org.opencontainers.image.vendor="Broadcom, Inc." \
org.opencontainers.image.version="1.16.3" org.opencontainers.image.version="1.16.4"
ENV HOME="/" \ ENV HOME="/" \
OS_ARCH="${TARGETARCH:-amd64}" \ OS_ARCH="${TARGETARCH:-amd64}" \
@@ -33,7 +33,7 @@ RUN mkdir -p /tmp/bitnami/pkg/cache/ ; cd /tmp/bitnami/pkg/cache/ ; \
"llvm-18.1.8-1-linux-${OS_ARCH}-debian-12" \ "llvm-18.1.8-1-linux-${OS_ARCH}-debian-12" \
"gops-0.3.28-10-linux-${OS_ARCH}-debian-12" \ "gops-0.3.28-10-linux-${OS_ARCH}-debian-12" \
"bpftool-7.5.0-0-linux-${OS_ARCH}-debian-12" \ "bpftool-7.5.0-0-linux-${OS_ARCH}-debian-12" \
"cilium-1.16.3-2-linux-${OS_ARCH}-debian-12" \ "cilium-1.16.4-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 \
@@ -51,7 +51,7 @@ RUN chmod g+rwX /opt/bitnami
COPY rootfs / COPY rootfs /
RUN /opt/bitnami/scripts/cilium/postunpack.sh RUN /opt/bitnami/scripts/cilium/postunpack.sh
ENV APP_VERSION="1.16.3" \ ENV APP_VERSION="1.16.4" \
BITNAMI_APP_NAME="cilium" BITNAMI_APP_NAME="cilium"
USER 1001 USER 1001

2
bitnami/cilium/1/debian-12/prebuildfs/opt/bitnami/.bitnami_components.json
View File

@@ -9,7 +9,7 @@
"arch": "amd64", "arch": "amd64",
"distro": "debian-12", "distro": "debian-12",
"type": "NAMI", "type": "NAMI",
"version": "1.16.3-2" "version": "1.16.4-0"
}, },
"gops": { "gops": {
"arch": "amd64", "arch": "amd64",

2
bitnami/cilium/1/debian-12/tags-info.yaml
View File

@@ -1,5 +1,5 @@
rolling-tags: rolling-tags:
- "1" - "1"
- 1-debian-12 - 1-debian-12
- 1.16.3 - 1.16.4
- latest - latest

4
bitnami/cilium/README.md
View File

@@ -26,11 +26,11 @@ Looking to use Cilium in production? Try [VMware Tanzu Application Catalog](http
## 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`.