[bitnami/nats] Release 2.12.7-debian-12-r0 (#92457)

Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>

bitnami/nats/2/debian-12/Dockerfile

@@ -17,7 +17,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=( \
-      "nats-2.12.6-1-linux-${OS_ARCH}-debian-12" \
+      "nats-2.12.7-0-linux-${OS_ARCH}-debian-12" \
     ) ; \
     for COMPONENT in "${COMPONENTS[@]}"; do \
       if [ ! -f "${COMPONENT}.tar.gz" ]; then \
@@ -40,20 +40,20 @@ ARG TARGETARCH
 ENV OS_ARCH="${TARGETARCH:-amd64}"
 
 LABEL org.opencontainers.image.base.name="scratch" \
-      org.opencontainers.image.created="2026-04-08T06:51:40Z" \
+      org.opencontainers.image.created="2026-04-14T16:43:51Z" \
       org.opencontainers.image.description="Application packaged by Broadcom, Inc." \
       org.opencontainers.image.title="nats" \
       org.opencontainers.image.vendor="Broadcom, Inc." \
-      org.opencontainers.image.version="2.12.6"
+      org.opencontainers.image.version="2.12.7"
 
 COPY rootfs /
 COPY --from=builder /opt/bitnami/nats/.spdx-nats.spdx /opt/bitnami/nats/.spdx-nats.spdx
 COPY --from=builder /opt/bitnami/nats/bin/nats-server /opt/bitnami/nats/bin/nats-server
 COPY --from=builder /opt/bitnami/nats/licenses /opt/bitnami/nats/licenses
 
-ENV APP_VERSION="2.12.6" \
+ENV APP_VERSION="2.12.7" \
     BITNAMI_APP_NAME="nats" \
-    IMAGE_REVISION="1" \
+    IMAGE_REVISION="0" \
     PATH="/opt/bitnami/nats/bin:$PATH"
 
 EXPOSE 4222 6222 8222

bitnami/nats/README.md

@@ -7,12 +7,18 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 
 ## TL;DR
 
-Use this quick command to run the container.
-
 ```console
 docker run -it --name nats bitnami/nats: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/nats/docker-compose.yml](https://github.com/bitnami/containers/tree/main/bitnami/nats/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/nats).
+
 ## 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?
@@ -46,90 +52,6 @@ Learn more about the Bitnami tagging policy and the difference between rolling t
 
 The Bitnami NATS 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/nats).
-
-## Connecting to other containers
-
-Using [Docker container networking](https://docs.docker.com/engine/userguide/networking/), a NATS server running inside a container can easily be accessed by your application containers using a NATS client.
-
-Containers attached to the same network can communicate with each other using the container name as the host name.
-
-### Using the command line
-
-In this example, we will create a NATS client instance that will connect to the server instance that is running on the same docker network as the client.
-
-1. Create a network
-
-    ```console
-    docker network create app-tier --driver bridge
-    ```
-
-2. Launch the NATS server instance
-
-    Use the `--network app-tier` argument to the `docker run` command to attach the NATS container to the `app-tier` network.
-
-    ```console
-    docker run -d --name nats-server \
-        --network app-tier \
-        --publish 4222:4222 \
-        --publish 6222:6222 \
-        --publish 8222:8222 \
-        --volume /path/to/nats-server.conf:/etc/nats-server.conf:ro \
-        bitnami/nats:latest -c /etc/nats-server.conf
-    ```
-
-3. Launch your NATS client instance
-
-You can create a NATS client instance as shown below:
-
-```console
-docker run -it --rm \
-    --network app-tier \
-    --volume /path/to/your/workspace:/go \
-    bitnami/natscli -s nats://nats-server:4222 <your-nats-command>
-```
-
-### Using a Docker Compose file
-
-When not specified, Docker Compose automatically sets up a new network and attaches all deployed services to that network. However, we will explicitly define a new `bridge` network named `app-tier`. In this example we assume that you want to connect to the NATS server from your own custom application image which is identified in the following snippet by the service name `myapp`.
-
-```yaml
-version: '2'
-
-networks:
-  app-tier:
-    driver: bridge
-
-services:
-  nats:
-    image: bitnami/nats:latest
-    ports:
-      - 4222:4222
-      - 6222:6222
-      - 8222:8222
-    networks:
-      - app-tier
-    volumes:
-      - /path/to/nats-server.conf:/etc/nats-server.conf:ro
-  myapp:
-    image: YOUR_APPLICATION_IMAGE
-    networks:
-      - app-tier
-```
-
-> **Important** 
-> 
-> 1. Update the `YOUR_APPLICATION_IMAGE` placeholder in the above snippet with your application image. 
-> 2. In your application container, use the host name `nats` to connect to the NATS server.
-
-Launch the containers using:
-
-```console
-docker-compose up -d
-```
-
 ## Configuration
 
 The following sections describe how to run commands and where to find further documentation.