[bitnami/nats] Release 2.9.14-debian-11-r3 (#24324)

Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
This commit is contained in:
Bitnami Bot 2023-02-17 17:44:57 +01:00 committed by GitHub
parent b5b5ac1200
commit 72bbb0d9bb
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 15 additions and 15 deletions

View File

@ -2,11 +2,11 @@ FROM docker.io/bitnami/minideb:bullseye
ARG TARGETARCH
LABEL org.opencontainers.image.authors="https://bitnami.com/contact" \
org.opencontainers.image.description="Application packaged by Bitnami" \
LABEL org.opencontainers.image.base.name="docker.io/bitnami/minideb:bullseye" \
org.opencontainers.image.created="2023-02-17T16:25:04Z" \
org.opencontainers.image.description="Application packaged by VMware, Inc" \
org.opencontainers.image.licenses="Apache-2.0" \
org.opencontainers.image.ref.name="2.9.14-debian-11-r2" \
org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/nats" \
org.opencontainers.image.ref.name="2.9.14-debian-11-r3" \
org.opencontainers.image.title="nats" \
org.opencontainers.image.vendor="VMware, Inc." \
org.opencontainers.image.version="2.9.14"
@ -22,9 +22,9 @@ SHELL ["/bin/bash", "-o", "pipefail", "-c"]
RUN install_packages ca-certificates curl procps
RUN mkdir -p /tmp/bitnami/pkg/cache/ && cd /tmp/bitnami/pkg/cache/ && \
COMPONENTS=( \
"render-template-1.0.5-0-linux-${OS_ARCH}-debian-11" \
"gosu-1.16.0-1-linux-${OS_ARCH}-debian-11" \
"nats-2.9.14-0-linux-${OS_ARCH}-debian-11" \
"render-template-1.0.5-1-linux-${OS_ARCH}-debian-11" \
"gosu-1.16.0-2-linux-${OS_ARCH}-debian-11" \
"nats-2.9.14-1-linux-${OS_ARCH}-debian-11" \
) && \
for COMPONENT in "${COMPONENTS[@]}"; do \
if [ ! -f "${COMPONENT}.tar.gz" ]; then \

View File

@ -1,23 +1,23 @@
{
"gosu": {
"arch": "amd64",
"digest": "9ab9654690d90d3c49ff66fb1eb286487e318adc899d036bc45922f6b176865b",
"digest": "f6056076afb745fd7d9d87d20f71e7248d63330352cf5ae0be2130b7f44a8cfa",
"distro": "debian-11",
"type": "NAMI",
"version": "1.16.0-1"
"version": "1.16.0-2"
},
"nats": {
"arch": "amd64",
"digest": "d2ed1f09789ad314ff82076965fee02d8ca14dafc6c7c6c52fd4b25c09d6f12c",
"digest": "74c4829737e1d3028c31b588f85e5df039501a27f859f5c3f01d8b3bf50b4ef1",
"distro": "debian-11",
"type": "NAMI",
"version": "2.9.14-0"
"version": "2.9.14-1"
},
"render-template": {
"arch": "amd64",
"digest": "57c1d857acbb187fcb98f4ba26d138af9d866f59ad38dd443a75c0a6422de994",
"digest": "185e277977366ec222d2bde1a395ffa138ce1a9d3bdf1df20c3e49e8b8f9c68b",
"distro": "debian-11",
"type": "NAMI",
"version": "1.0.5-0"
"version": "1.0.5-1"
}
}

View File

@ -128,7 +128,7 @@ docker run -it --rm \
golang ./nats-pub.sh foo bar
```
### Using Docker Compose
### 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`.
@ -233,7 +233,7 @@ docker run -d --name nats -p 4222:4222 -p 6222:6222 -p 8222:8222 \
bitnami/nats:latest
```
#### Using Docker Compose deployment
#### Deploying a Docker Compose file
Modify the [`docker-compose.yml`](https://github.com/bitnami/containers/blob/main/bitnami/nats/docker-compose.yml) file present in this repository as follows: