xray-rabbitmq upgrade issue
Summary
I'm opening this related issue with the confidential flag turned off. I'm not sure if my ticket is being ignored, or if it's just not visible by the support engineers for this Repo. I have also opened a support ticket at support.jfrog.com #291302 to work this from the Jfrog support angle as well.
We would like to know:
- How this container is working in other environments with the bug mentioned below
- Is there some environment variables we can set rather than doing the rm commands in the Dockerfile
- Can the /opt/bitnami/common/bin/gosu binary be updated to remove the CAT 1 finding for this container image.
- When will a new release be created for xray-rabbitmq, since the 3.86.10 image is 3 month old and 3.91.3 is the latest version of Xray.
Steps to reproduce
When upgrading from 3.67.9 to any later image in IronBank and enabling BITNAMI_DEBUG=true, we are seeing this issue with rabbitmq when it goes to start:
/opt/bitnami/erlang/lib/erlang/erts-13.2/bin/beam.smp: /lib64/libtinfo.so.6: no version information available (required by /opt/bitnami/erlang/lib/erlang/erts-13.2/bin/beam.smp)
/opt/bitnami/erlang/lib/erlang/erts-13.2/bin/beam.smp: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by /opt/bitnami/erlang/lib/erlang/erts-13.2/bin/beam.smp)
In our case we are upgrading xray-rabbitmq from 3.67.9 to 3.86.10, also seeing when running 3.86.10 brand new or with any of the other containers past 3.67.9 in Harbor
What is the current bug behavior?
rabbitmq 19:01:06.58
rabbitmq 19:01:06.58 Welcome to the Bitnami rabbitmq container
rabbitmq 19:01:06.58 Subscribe to project updates by watching https://github.com/bitnami/containers
rabbitmq 19:01:06.59 Submit issues and feature requests at https://github.com/bitnami/containers/issues
rabbitmq 19:01:06.59
rabbitmq 19:01:06.59 INFO ==> ** Starting RabbitMQ setup **
rabbitmq 19:01:06.61 INFO ==> Validating settings in RABBITMQ_* env vars..
rabbitmq 19:01:06.63 INFO ==> Initializing RabbitMQ...
rabbitmq 19:01:06.64 DEBUG ==> Creating configuration file...
rabbitmq 19:01:06.65 DEBUG ==> Creating environment file...
rabbitmq 19:01:06.65 DEBUG ==> Creating enabled_plugins file...
rabbitmq 19:01:06.66 DEBUG ==> Creating Erlang cookie...
rabbitmq 19:01:06.66 INFO ==> Generating random cookie
rabbitmq 19:01:06.67 DEBUG ==> Ensuring expected directories/files exist...
rabbitmq 19:01:06.69 INFO ==> Starting RabbitMQ in background...
/opt/bitnami/erlang/lib/erlang/erts-13.2/bin/beam.smp: /lib64/libtinfo.so.6: no version information available (required by /opt/bitnami/erlang/lib/erlang/erts-13.2/bin/beam.smp)
/opt/bitnami/erlang/lib/erlang/erts-13.2/bin/beam.smp: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by /opt/bitnami/erlang/lib/erlang/erts-13.2/bin/beam.smp)
rabbitmq 19:03:06.69 ERROR ==> Couldn't start RabbitMQ in background.
What is the expected correct behavior?
rabbitmq 19:01:14.90 INFO ==> No custom scripts in /docker-entrypoint-initdb.d
rabbitmq 19:01:14.90 INFO ==> Stopping RabbitMQ...
Stopping and halting node rabbit@localhost ...
Gracefully halting Erlang VM
rabbitmq 19:01:22.56 INFO ==> ** RabbitMQ setup finished! **
rabbitmq 19:01:22.56 INFO ==> ** Starting RabbitMQ **
Relevant logs and/or screenshots
shown above
Possible fixes
I've used this solution in the Dockerfile, but maybe there is a better way. Note: Removing gosu is only done to remove a CAT 1 security finding the two line above that is what is the fix for this bug.
&& rm -rf /opt/bitnami/erlang/lib/erlang; ln -s /usr/lib64/erlang /opt/bitnami/erlang/lib/erlang \
&& rm -rf /opt/bitnami/erlang/bin; ln -s /usr/lib64/erlang/bin /opt/bitnami/erlang/bin \
&& rm -rf /opt/bitnami/common/bin/gosu
Tasks
-
Bug has been identified and corrected within the container
Please read the Iron Bank Documentation for more info
Please read the Iron Bank Documentation for more info