[bitnami/consul] Release 1.22.7-debian-12-r0 (#92647)

Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>
This commit is contained in:
Bitnami Bot
2026-04-25 10:55:07 +02:00
committed by GitHub
parent 3757e901f3
commit c927a0ad75
2 changed files with 13 additions and 23 deletions
+5 -5
View File
@@ -7,13 +7,13 @@ 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-08T00:45:24Z" \
org.opencontainers.image.created="2026-04-25T08:45:43Z" \
org.opencontainers.image.description="Application packaged by Broadcom, Inc." \
org.opencontainers.image.documentation="https://github.com/bitnami/containers/tree/main/bitnami/consul/README.md" \
org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/consul" \
org.opencontainers.image.title="consul" \
org.opencontainers.image.vendor="Broadcom, Inc." \
org.opencontainers.image.version="1.22.6"
org.opencontainers.image.version="1.22.7"
ENV HOME="/" \
OS_ARCH="${TARGETARCH:-amd64}" \
@@ -29,7 +29,7 @@ RUN --mount=type=secret,id=downloads_url,env=SECRET_DOWNLOADS_URL \
mkdir -p /tmp/bitnami/pkg/cache/ ; cd /tmp/bitnami/pkg/cache/ || exit 1 ; \
COMPONENTS=( \
"render-template-1.0.9-164-linux-${OS_ARCH}-debian-12" \
"consul-1.22.6-1-linux-${OS_ARCH}-debian-12" \
"consul-1.22.7-0-linux-${OS_ARCH}-debian-12" \
) ; \
for COMPONENT in "${COMPONENTS[@]}"; do \
if [ ! -f "${COMPONENT}.tar.gz" ]; then \
@@ -48,9 +48,9 @@ RUN uninstall_packages curl
COPY rootfs /
RUN /opt/bitnami/scripts/consul/postunpack.sh
ENV APP_VERSION="1.22.6" \
ENV APP_VERSION="1.22.7" \
BITNAMI_APP_NAME="consul" \
IMAGE_REVISION="1" \
IMAGE_REVISION="0" \
PATH="/opt/bitnami/common/bin:/opt/bitnami/consul/bin:$PATH"
EXPOSE 8300 8301 8500 8600
+8 -18
View File
@@ -11,7 +11,13 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
docker run --name consul bitnami/consul:latest
```
You can find the available configuration options in the [Environment Variables](#environment-variables) section.
## 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/consul/docker-compose.yml](https://github.com/bitnami/containers/tree/main/bitnami/consul/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/consul).
## Why use Bitnami Secure Images?
@@ -46,10 +52,6 @@ Learn more about the Bitnami tagging policy and the difference between rolling t
The Bitnami HashiCorp Consul 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/consul).
## Persisting your application
If you remove the container all your data and configurations will be lost, and the next time you run the image the database will be reinitialized. To avoid this loss of data, you should mount a volume that will persist even after the container is removed.
@@ -168,19 +170,7 @@ The Bitnami HashiCorp Consul Docker image from the [Bitnami Secure Images](https
## Logging
The Bitnami consul Docker image sends the container logs to the `stdout`. To view the logs:
```console
docker logs consul
```
or using Docker Compose:
```console
docker-compose logs consul
```
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 HashiCorp Consul 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.
## Notable Changes