public_git
/
bitnami-containers
mirror of https://github.com/bitnami/containers.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

[bitnami/rabbitmq] Release 3.9.28-debian-11-r6 (#24377) 

Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
This commit is contained in:
Bitnami Bot 2023-02-17 19:16:24 +01:00 committed by GitHub
parent cf1913c0ce
commit 502dfc1b02
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 17 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
bitnami/rabbitmq/3.9/debian-11/Dockerfile
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-17T17:42:54Z" \
org.opencontainers.image.description="Application packaged by VMware, Inc" \
org.opencontainers.image.licenses="Apache-2.0" \
org.opencontainers.image.ref.name="3.9.28-debian-11-r5" \
org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/rabbitmq" \
org.opencontainers.image.ref.name="3.9.28-debian-11-r6" \
org.opencontainers.image.title="rabbitmq" \
org.opencontainers.image.vendor="VMware, Inc." \
org.opencontainers.image.version="3.9.28"
@ -23,9 +23,9 @@ SHELL ["/bin/bash", "-o", "pipefail", "-c"]
RUN install_packages ca-certificates curl libgcc-s1 libssl1.1 libstdc++6 libtinfo6 locales procps zlib1g
RUN mkdir -p /tmp/bitnami/pkg/cache/ && cd /tmp/bitnami/pkg/cache/ && \
COMPONENTS=( \
"gosu-1.16.0-1-linux-${OS_ARCH}-debian-11" \
"erlang-24.3.4-8-1-linux-${OS_ARCH}-debian-11" \
"rabbitmq-3.9.28-0-linux-${OS_ARCH}-debian-11" \
"gosu-1.16.0-2-linux-${OS_ARCH}-debian-11" \
"erlang-24.3.4-8-2-linux-${OS_ARCH}-debian-11" \
"rabbitmq-3.9.28-1-linux-${OS_ARCH}-debian-11" \
) && \
for COMPONENT in "${COMPONENTS[@]}"; do \
if [ ! -f "${COMPONENT}.tar.gz" ]; then \

12
bitnami/rabbitmq/3.9/debian-11/prebuildfs/opt/bitnami/.bitnami_components.json
View File

@ -1,23 +1,23 @@
{
"erlang": {
"arch": "amd64",
"digest": "92d81089e78d119ee6fd68096756d379f3938c6b5f4e7ae2e390697c72bc03ae",
"digest": "f3fa0adc90a3550305ac9709c8a8027bc6281e049d9d9035d25da0de9cc5f21d",
"distro": "debian-11",
"type": "NAMI",
"version": "24.3.4-8-1"
"version": "24.3.4-8-2"
},
"gosu": {
"arch": "amd64",
"digest": "9ab9654690d90d3c49ff66fb1eb286487e318adc899d036bc45922f6b176865b",
"digest": "f6056076afb745fd7d9d87d20f71e7248d63330352cf5ae0be2130b7f44a8cfa",
"distro": "debian-11",
"type": "NAMI",
"version": "1.16.0-1"
"version": "1.16.0-2"
},
"rabbitmq": {
"arch": "amd64",
"digest": "e0943940eede6c7cb2abb9d85a2bbb5a8a9a365f0ad1867835ffcedec4e21a63",
"digest": "64b84debf3756086d0c6e10dc173d53071aaf93f06524df03e10ea57b5a87f68",
"distro": "debian-11",
"type": "NAMI",
"version": "3.9.28-0"
"version": "3.9.28-1"
}
}

8
bitnami/rabbitmq/README.md
View File

@ -132,7 +132,7 @@ docker run -it --rm \
bitnami/rabbitmq:latest rabbitmqctl -n rabbit@rabbitmq-server status
```
### 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 RabbitMQ server from your own custom application image which is identified in the following snippet by the service name `myapp`.
@ -241,11 +241,11 @@ Available variables:
### Setting up a cluster
#### Docker Compose deployment
### Using Docker Compose
This is the simplest way to run RabbitMQ with clustering configuration:
##### Step 1: Add a stats node in your `docker-compose.yml`
#### Step 1: Add a stats node in your `docker-compose.yml`
Copy the snippet below into your docker-compose.yml to add a RabbitMQ stats node to your cluster configuration.
@ -417,7 +417,7 @@ docker run --name openldap \
To configure authorization, you need to create an advanced.config file, following the [clasic config format](https://www.rabbitmq.com/configure.html#erlang-term-config-file), and add your authorization rules. For instance, use the file below to grant all users the ability to use the management plugin, but make none of them administrators:
```config
```text
[{rabbitmq_auth_backend_ldap,[
{tag_queries, [{administrator, {constant, false}},
{management, {constant, true}}]}