From 8d61af0f0b234db64f74e0e0f20ed00992a3b576 Mon Sep 17 00:00:00 2001 From: Bitnami Bot Date: Thu, 23 Apr 2026 03:54:57 +0200 Subject: [PATCH] [bitnami/rabbitmq] Release 4.2.6-debian-12-r0 (#92607) Signed-off-by: Bitnami Bot --- bitnami/rabbitmq/4.2/debian-12/Dockerfile | 10 ++++---- bitnami/rabbitmq/README.md | 28 ++++++++--------------- 2 files changed, 14 insertions(+), 24 deletions(-) diff --git a/bitnami/rabbitmq/4.2/debian-12/Dockerfile b/bitnami/rabbitmq/4.2/debian-12/Dockerfile index 5ebceb8d3f20..84bc82031251 100644 --- a/bitnami/rabbitmq/4.2/debian-12/Dockerfile +++ b/bitnami/rabbitmq/4.2/debian-12/Dockerfile @@ -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-08T21:00:39Z" \ + org.opencontainers.image.created="2026-04-23T01:38:54Z" \ org.opencontainers.image.description="Application packaged by Broadcom, Inc." \ org.opencontainers.image.documentation="https://github.com/bitnami/containers/tree/main/bitnami/rabbitmq/README.md" \ org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/rabbitmq" \ org.opencontainers.image.title="rabbitmq" \ org.opencontainers.image.vendor="Broadcom, Inc." \ - org.opencontainers.image.version="4.2.5" + org.opencontainers.image.version="4.2.6" ENV HOME="/opt/bitnami/rabbitmq/.rabbitmq" \ OS_ARCH="${TARGETARCH:-amd64}" \ @@ -30,7 +30,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=( \ "erlang-27.3.4-3-linux-${OS_ARCH}-debian-12" \ - "rabbitmq-4.2.5-0-linux-${OS_ARCH}-debian-12" \ + "rabbitmq-4.2.6-0-linux-${OS_ARCH}-debian-12" \ ) ; \ for COMPONENT in "${COMPONENTS[@]}"; do \ if [ ! -f "${COMPONENT}.tar.gz" ]; then \ @@ -52,9 +52,9 @@ RUN /opt/bitnami/scripts/locales/generate-locales.sh COPY rootfs / RUN /opt/bitnami/scripts/rabbitmq/postunpack.sh -ENV APP_VERSION="4.2.5" \ +ENV APP_VERSION="4.2.6" \ BITNAMI_APP_NAME="rabbitmq" \ - IMAGE_REVISION="1" \ + IMAGE_REVISION="0" \ LANG="en_US.UTF-8" \ LANGUAGE="en_US:en" diff --git a/bitnami/rabbitmq/README.md b/bitnami/rabbitmq/README.md index 08069e72a867..d39b8adcdd3c 100644 --- a/bitnami/rabbitmq/README.md +++ b/bitnami/rabbitmq/README.md @@ -13,6 +13,14 @@ docker run --name rabbitmq bitnami/rabbitmq:latest You can find the default credentials and 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/rabbitmq/docker-compose.yml](https://github.com/bitnami/containers/tree/main/bitnami/rabbitmq/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/rabbitmq). + ## 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,10 +54,6 @@ Learn more about the Bitnami tagging policy and the difference between rolling t The Bitnami RabbitMQ 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/rabbitmq). - ## Persisting your application If you remove the container all your data 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. @@ -146,8 +150,6 @@ The following tables list the main variables you can set. | `RABBITMQ_MNESIA_BASE` | Path to RabbitMQ mnesia directory. | `$RABBITMQ_DATA_DIR` | | `RABBITMQ_COMBINED_CERT_PATH` | Path to the RabbitMQ server SSL certificate key file. | `${RABBITMQ_COMBINED_CERT_PATH:-/tmp/rabbitmq_combined_keys.pem}` | -When you start the rabbitmq image, you can adjust the configuration of the instance by passing one or more environment variables either on the docker-compose file or on the `docker run` command line. - ### Configuration file A custom `rabbitmq.conf` configuration file can be mounted to the `/bitnami/rabbitmq/conf` directory. If no file is mounted, the container will generate a default one based on the environment variables. You can also mount on this directory your own `advanced.config` (using classic Erlang terms) and `rabbitmq-env.conf` configuration files. @@ -185,19 +187,7 @@ Follow these instructions to use the [Bitnami Docker OpenLDAP](https://github.co ## Logging -The Bitnami RabbitMQ Docker image sends the container logs to the `stdout`. To view the logs: - -```console -docker logs rabbitmq -``` - -or using Docker Compose: - -```console -docker-compose logs rabbitmq -``` - -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 RabbitMQ 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