[bitnami/kong] Release kong-3.8.1-debian-12-r0 (#74989)

Signed-off-by: Bitnami Bot <bitnami-bot@vmware.com>
This commit is contained in:
Bitnami Bot
2024-11-19 01:14:33 +01:00
committed by GitHub
parent 3819d6f2f4
commit d02735922b
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-09T21:33:49Z" \ org.opencontainers.image.created="2024-11-18T23:49:27Z" \
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/kong/README.md" \ org.opencontainers.image.documentation="https://github.com/bitnami/containers/tree/main/bitnami/kong/README.md" \
org.opencontainers.image.licenses="Apache-2.0" \ org.opencontainers.image.licenses="Apache-2.0" \
org.opencontainers.image.ref.name="3.8.0-debian-12-r10" \ org.opencontainers.image.ref.name="3.8.1-debian-12-r0" \
org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/kong" \ org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/kong" \
org.opencontainers.image.title="kong" \ org.opencontainers.image.title="kong" \
org.opencontainers.image.vendor="Broadcom, Inc." \ org.opencontainers.image.vendor="Broadcom, Inc." \
org.opencontainers.image.version="3.8.0" org.opencontainers.image.version="3.8.1"
ENV HOME="/" \ ENV HOME="/" \
OS_ARCH="${TARGETARCH:-amd64}" \ OS_ARCH="${TARGETARCH:-amd64}" \
@@ -30,7 +30,7 @@ RUN install_packages ca-certificates curl libabsl20220623 libaom3 libavif15 libb
RUN mkdir -p /tmp/bitnami/pkg/cache/ ; cd /tmp/bitnami/pkg/cache/ ; \ RUN mkdir -p /tmp/bitnami/pkg/cache/ ; cd /tmp/bitnami/pkg/cache/ ; \
COMPONENTS=( \ COMPONENTS=( \
"render-template-1.0.7-7-linux-${OS_ARCH}-debian-12" \ "render-template-1.0.7-7-linux-${OS_ARCH}-debian-12" \
"kong-3.8.0-5-linux-${OS_ARCH}-debian-12" \ "kong-3.8.1-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 \
@@ -48,7 +48,7 @@ RUN find / -perm /6000 -type f -exec chmod a-s {} \; || true
COPY rootfs / COPY rootfs /
RUN /opt/bitnami/scripts/kong/postunpack.sh RUN /opt/bitnami/scripts/kong/postunpack.sh
ENV APP_VERSION="3.8.0" \ ENV APP_VERSION="3.8.1" \
BITNAMI_APP_NAME="kong" \ BITNAMI_APP_NAME="kong" \
PATH="/opt/bitnami/common/bin:/opt/bitnami/kong/bin:/opt/bitnami/kong/luarocks/bin:/opt/bitnami/kong/openresty/bin:/opt/bitnami/kong/openresty/luajit/bin:/opt/bitnami/kong/openresty/nginx/sbin:$PATH" PATH="/opt/bitnami/common/bin:/opt/bitnami/kong/bin:/opt/bitnami/kong/luarocks/bin:/opt/bitnami/kong/openresty/bin:/opt/bitnami/kong/openresty/luajit/bin:/opt/bitnami/kong/openresty/nginx/sbin:$PATH"

View File

@@ -3,7 +3,7 @@
"arch": "amd64", "arch": "amd64",
"distro": "debian-12", "distro": "debian-12",
"type": "NAMI", "type": "NAMI",
"version": "3.8.0-5" "version": "3.8.1-0"
}, },
"render-template": { "render-template": {
"arch": "amd64", "arch": "amd64",

View File

@@ -1,5 +1,5 @@
rolling-tags: rolling-tags:
- "3" - "3"
- 3-debian-12 - 3-debian-12
- 3.8.0 - 3.8.1
- latest - latest

View File

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