3.7.7-debian-9-r35 release

Add support for hashed-passwords

bitnami/rabbitmq/3.7/debian-9/Dockerfile

@@ -9,17 +9,18 @@ ENV BITNAMI_PKG_CHMOD="-R g+rwX" \
 # Install required system packages and dependencies
 RUN install_packages libc6 libssl1.1 libtinfo5 zlib1g
 RUN bitnami-pkg install erlang-21.0.0-1 --checksum 49cc464088d9b120db6eaca79bcd3735d31c72a2e7a773801c7545c23a26cab4
-RUN bitnami-pkg unpack rabbitmq-3.7.7-3 --checksum efd2720aaae4a08fb4cbd2f6dc4deac6ffac293871c7debbfc965d1179299b75
+RUN bitnami-pkg unpack rabbitmq-3.7.7-4 --checksum 73bbcce3d40b158ffc6a3d851fce13211ccad817db678d17f7ec3cee17ffddec
 RUN mkdir -p /opt/bitnami/rabbitmq/.rabbitmq && mkdir -p /opt/bitnami/rabbitmq/var/log/rabbitmq && chmod g+rwX -R /opt/bitnami/rabbitmq/.rabbitmq /opt/bitnami/rabbitmq/var
 
 COPY rootfs /
 ENV BITNAMI_APP_NAME="rabbitmq" \
-    BITNAMI_IMAGE_VERSION="3.7.7-debian-9-r34" \
+    BITNAMI_IMAGE_VERSION="3.7.7-debian-9-r35" \
     PATH="/opt/bitnami/erlang/bin:/opt/bitnami/rabbitmq/bin:/opt/bitnami/rabbitmq/sbin:$PATH" \
     RABBITMQ_CLUSTER_NODE_NAME="" \
     RABBITMQ_CLUSTER_PARTITION_HANDLING="ignore" \
     RABBITMQ_DISK_FREE_LIMIT="{mem_relative, 1.0}" \
     RABBITMQ_ERL_COOKIE="" \
+    RABBITMQ_HASHED_PASSWORD="" \
     RABBITMQ_MANAGER_PORT_NUMBER="15672" \
     RABBITMQ_NODE_NAME="rabbit@localhost" \
     RABBITMQ_NODE_PORT_NUMBER="5672" \

bitnami/rabbitmq/3.7/debian-9/rootfs/rabbitmq-inputs.json

@@ -3,6 +3,7 @@
   "clusterPartitionHandling": "{{$global.env.RABBITMQ_CLUSTER_PARTITION_HANDLING}}",
   "diskFreeLimit": "{{$global.env.RABBITMQ_DISK_FREE_LIMIT}}",
   "erlangCookie": "{{$global.env.RABBITMQ_ERL_COOKIE}}",
+  "hashedPassword": "{{$global.env.RABBITMQ_HASHED_PASSWORD}}",
   "managerPort": "{{$global.env.RABBITMQ_MANAGER_PORT_NUMBER}}",
   "nodeName": "{{$global.env.RABBITMQ_NODE_NAME}}",
   "nodePort": "{{$global.env.RABBITMQ_NODE_PORT_NUMBER}}",

bitnami/rabbitmq/README.md

@@ -34,9 +34,11 @@ $ docker-compose up -d
 
 > NOTE: Debian 8 images have been deprecated in favor of Debian 9 images. Bitnami will not longer publish new Docker images based on Debian 8.
 
+Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags [in our documentation page](https://docs.bitnami.com/containers/how-to/understand-rolling-tags-containers/).
+
 
 * [`3.7-ol-7`, `3.7.7-ol-7-r30` (3.7/ol-7/Dockerfile)](https://github.com/bitnami/bitnami-docker-rabbitmq/blob/3.7.7-ol-7-r30/3.7/ol-7/Dockerfile)
-* [`3.7-debian-9`, `3.7.7-debian-9-r34`, `3.7`, `3.7.7`, `3.7.7-r34`, `latest` (3.7/Dockerfile)](https://github.com/bitnami/bitnami-docker-rabbitmq/blob/3.7.7-debian-9-r34/3.7/Dockerfile)
+* [`3.7-debian-9`, `3.7.7-debian-9-r35`, `3.7`, `3.7.7`, `3.7.7-r35`, `latest` (3.7/Dockerfile)](https://github.com/bitnami/bitnami-docker-rabbitmq/blob/3.7.7-debian-9-r35/3.7/Dockerfile)
 
 Subscribe to project updates by watching the [bitnami/rabbitmq GitHub repo](https://github.com/bitnami/bitnami-docker-rabbitmq).
 
@@ -173,6 +175,7 @@ Available variables:
 
  - `RABBITMQ_USERNAME`: RabbitMQ application username. Default: **user**
  - `RABBITMQ_PASSWORD`: RabbitMQ application password. Default: **bitnami**
+ - `RABBITMQ_HASHED_PASSWORD`: RabbitMQ application hasehd password.
  - `RABBITMQ_VHOST`: RabbitMQ application vhost. Default: **/**
  - `RABBITMQ_ERL_COOKIE`: Erlang cookie to determine whether different nodes are allowed to communicate with each other.
  - `RABBITMQ_NODE_TYPE`: Node Type. Valid values: *stats*, *queue-ram* or *queue-disc*. Default: **stats**
@@ -427,6 +430,11 @@ $ docker-compose up rabbitmq
 
 # Notable changes
 
+## 3.7.7-r30
+
+- The RabbitMQ container includes a new environment variable `RABBITMQ_HASHED_PASSWORD` that allows setting password via SHA256 hash (consult [official documentation](https://www.rabbitmq.com/passwords.html) for more information about password hashes).
+- Please note that password hashes must be generated following the [official algorithm](https://www.rabbitmq.com/passwords.html#computing-password-hash). You can use [this Python script](https://gist.githubusercontent.com/anapsix/4c3e8a8685ce5a3f0d7599c9902fd0d5/raw/1203a480fcec1982084b3528415c3cad26541b82/rmq_passwd_hash.py) to generate them.
+
 ## 3.7.7-r19
 
 - The RabbitMQ container has been migrated to a non-root user approach. Previously the container ran as the `root` user and the RabbitMQ daemon was started as the `rabbitmq` user. From now on, both the container and the RabbitMQ daemon run as user `1001`. As a consequence, the data directory must be writable by that user. You can revert this behavior by changing `USER 1001` to `USER root` in the Dockerfile.