Closed JonasKunz closed 2 months ago
Did some quick experiments, looks like statically linking musl in a shared library is not a good idea, because it will still operate on the same shared resources as the JVM-process. This causes problems e.g. with malloc.
So I guess the best solution is to provide separate musl-variants of the binaries and detect musl at runtime.
In case someone wants the full error log from a recent build of alpine with gcompat hs_err_pid45.log
Currently the universal-profiling-integration crashes on linux distros shipping musl instead of glibc (e.g. Alpine):
This can only be prevented at the moment by disabling the profiling integration via
ELASTIC_OTEL_UNIVERSAL_PROFILING_INTEGRATION_ENABLED=false
.We should fix this by either: