Open clagms opened 1 year ago
@gitting-around is there any way to fix these dependency issues once and for all? It's a nuissance that whenever a new ubuntu version comes about, we risk breaking rabbitmqfmu loading behavior.
Can we at least set up integration tests that will catch these problems? They are fairly easy to reproduce: just get a docker with latest ubuntu, and run a cosim with rabbitmq and some script generating messages.
The workaround to this issue is to change the dockerfile above with the following:
FROM ubuntu:22.04
RUN DEBIAN_FRONTEND=noninteractive
RUN apt-get update && apt-get install -y openjdk-11-jdk
# Fixes https://github.com/INTO-CPS-Association/fmu-rabbitmq/issues/57
RUN echo "deb http://security.ubuntu.com/ubuntu focal-security main" | tee --append /etc/apt/sources.list
RUN apt-get update && apt-get install -y libicu66 libssl1.1
CMD tail -F anything
Maybe RabbitmqFMU needs to be updated to use the most recent openssl? It seems the intention is to move away from openssl1
I just noticed that this seems to be a duplicate of https://github.com/INTO-CPS-Association/fmu-rabbitmq/issues/56 and https://github.com/INTO-CPS-Association/fmu-rabbitmq/issues/54.
I hope we can find another solution to prevent this from reocurring whenever ubuntu changes.
It seems that if Rabbitmq is loaded in a dockerfile like the following, it will fail due to missing dependency:
As of today, the latest ubuntu is 22.04
It will give the following error: