From db376ac0e7ab4c3bcf7ca4b6172be3ea40ab6799 Mon Sep 17 00:00:00 2001 From: Bitnami Bot Date: Fri, 24 Apr 2026 13:15:44 +0200 Subject: [PATCH] [bitnami/kong] Release 3.9.1-debian-12-r38 (#92633) Signed-off-by: Bitnami Bot --- bitnami/kong/3/debian-12/Dockerfile | 6 +++--- bitnami/kong/README.md | 20 +++++++++----------- 2 files changed, 12 insertions(+), 14 deletions(-) diff --git a/bitnami/kong/3/debian-12/Dockerfile b/bitnami/kong/3/debian-12/Dockerfile index 073aa7c9ffc9..eea4897e61ef 100644 --- a/bitnami/kong/3/debian-12/Dockerfile +++ b/bitnami/kong/3/debian-12/Dockerfile @@ -7,7 +7,7 @@ ARG DOWNLOADS_URL="downloads.bitnami.com/files/stacksmith" ARG TARGETARCH LABEL org.opencontainers.image.base.name="docker.io/bitnami/minideb:bookworm" \ - org.opencontainers.image.created="2026-04-08T19:34:16Z" \ + org.opencontainers.image.created="2026-04-24T11:00:17Z" \ 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.source="https://github.com/bitnami/containers/tree/main/bitnami/kong" \ @@ -28,7 +28,7 @@ RUN --mount=type=secret,id=downloads_url,env=SECRET_DOWNLOADS_URL \ DOWNLOADS_URL=${SECRET_DOWNLOADS_URL:-${DOWNLOADS_URL}} ; \ mkdir -p /tmp/bitnami/pkg/cache/ ; cd /tmp/bitnami/pkg/cache/ || exit 1 ; \ COMPONENTS=( \ - "kong-3.9.1-18-linux-${OS_ARCH}-debian-12" \ + "kong-3.9.1-19-linux-${OS_ARCH}-debian-12" \ ) ; \ for COMPONENT in "${COMPONENTS[@]}"; do \ if [ ! -f "${COMPONENT}.tar.gz" ]; then \ @@ -48,7 +48,7 @@ COPY rootfs / RUN /opt/bitnami/scripts/kong/postunpack.sh ENV APP_VERSION="3.9.1" \ BITNAMI_APP_NAME="kong" \ - IMAGE_REVISION="37" \ + IMAGE_REVISION="38" \ PATH="/opt/bitnami/kong/bin:/opt/bitnami/kong/openresty/bin:/opt/bitnami/kong/openresty/luajit/bin:/opt/bitnami/kong/openresty/nginx/sbin:/opt/bitnami/kong/luarocks/bin:$PATH" EXPOSE 8000 8001 8443 8444 diff --git a/bitnami/kong/README.md b/bitnami/kong/README.md index 33e4448bf495..94bc2d264ef2 100644 --- a/bitnami/kong/README.md +++ b/bitnami/kong/README.md @@ -11,6 +11,14 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema docker run --name kong bitnami/kong:latest ``` +## Using `docker-compose.yml` + +The docker-compose.yaml file of this container can be found in the [Bitnami Containers repository](https://github.com/bitnami/containers/). + +[https://github.com/bitnami/containers/tree/main/bitnami/kong/docker-compose.yml](https://github.com/bitnami/containers/tree/main/bitnami/kong/docker-compose.yml) + +Please be aware this file has not undergone internal testing. Consequently, we advise its use exclusively for development or testing purposes. For production-ready deployments, we highly recommend utilizing its associated [Bitnami Helm chart](https://github.com/bitnami/charts/tree/main/bitnami/kong). + ## Why use Bitnami Secure Images? Those are hardened, minimal CVE images built and maintained by Bitnami. Bitnami Secure Images are based on the cloud-optimized, security-hardened enterprise [OS Photon Linux](https://vmware.github.io/photon/). Why choose BSI images? @@ -40,10 +48,6 @@ Learn more about the Bitnami tagging policy and the difference between rolling t The Bitnami Kong Docker image is only available to [Bitnami Secure Images](https://bitnami.com) customers. -## Using `docker-compose.yaml` - -Please be aware this file has not undergone internal testing. Consequently, we advise its use exclusively for development or testing purposes. For production-ready deployments, we highly recommend utilizing its associated [Bitnami Helm chart](https://github.com/bitnami/charts/tree/main/bitnami/kong). - ## Connecting to other containers Using [Docker container networking](https://docs.docker.com/engine/userguide/networking/), a different server running inside a container can easily be accessed by your application containers and vice-versa. @@ -159,13 +163,7 @@ The Bitnami Kong Docker image from the [Bitnami Secure Images](https://go-vmware ## Logging -The Bitnami Kong Docker image sends the container logs to `stdout`. To view the logs: - -```console -docker logs kong -``` - -You can configure the containers [logging driver](https://docs.docker.com/engine/admin/logging/overview/) using the `--log-driver` option if you wish to consume the container logs differently. In the default configuration docker uses the `json-file` driver. +The Bitnami Kong Docker image sends the container logs to the `stdout`. You can configure the containers [logging driver](https://docs.docker.com/engine/admin/logging/overview/) using the `--log-driver` option if you wish to consume the container logs differently. In the default configuration docker uses the `json-file` driver. ## Customize this image