[bitnami/rabbitmq] Release 3.10.25-debian-11-r44 (#47360)

Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
This commit is contained in:
Bitnami Bot 2023-09-05 02:06:11 +02:00 committed by GitHub
parent 51cd31ffd3
commit a2fed7e177
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 5 additions and 2 deletions

View File

@ -7,10 +7,10 @@ ARG TARGETARCH
LABEL com.vmware.cp.artifact.flavor="sha256:1e1b4657a77f0d47e9220f0c37b9bf7802581b93214fff7d1bd2364c8bf22e8e" \
org.opencontainers.image.base.name="docker.io/bitnami/minideb:bullseye" \
org.opencontainers.image.created="2023-09-01T13:28:29Z" \
org.opencontainers.image.created="2023-09-04T14:40:57Z" \
org.opencontainers.image.description="Application packaged by VMware, Inc" \
org.opencontainers.image.licenses="Apache-2.0" \
org.opencontainers.image.ref.name="3.10.25-debian-11-r41" \
org.opencontainers.image.ref.name="3.10.25-debian-11-r44" \
org.opencontainers.image.title="rabbitmq" \
org.opencontainers.image.vendor="VMware, Inc." \
org.opencontainers.image.version="3.10.25"

View File

@ -36,6 +36,9 @@ for entry in "${symlinks[@]}"; do
ln -s "$file" "$link"
done
# Additionally, ensure that the /var/log is accessible, which may have been hardened
chmod g+x /var/log
# Special case for RabbitMQ mnesia dir, which will have a different symbolic linking to ensure compatibility with
# the RabbitMQ Cluster Operator