You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using newly built JRE 17 for deployment in k8s, it is common to use musl as replacement for glibc. Snappy Java fail to run since it requires the glibc. Error message indicate it requires /lib64/ld-linux-x86-64.so.2
Load glibc apk did not work. It trigger a mother led problm. Seems like it’s not possible to have both musl and glibc linked into same process (make sense - they both attempt to provide the same libraries).
I did not try the compt-glibc5, which was suggested in some forum (yet)
my ask: in the spirit of minimizing image size for k8s system - possible to change the snappy Java code
Bundle a native build of snappy against MUSL library (in addition to the glibc build)
Bundle the musl based code library into the jar file
Detect a MUSL-based JVM (or thru setting), and use the musl native library in this case (plus opt out, as safety net).
Having MUSL support built in will be a step forward to help deployments of snappy Java (we use it as part or parquet Java) - it willl eliminate lot of wasted time on runtime errors
The text was updated successfully, but these errors were encountered:
When using newly built JRE 17 for deployment in k8s, it is common to use musl as replacement for glibc. Snappy Java fail to run since it requires the glibc. Error message indicate it requires /lib64/ld-linux-x86-64.so.2
Load glibc apk did not work. It trigger a mother led problm. Seems like it’s not possible to have both musl and glibc linked into same process (make sense - they both attempt to provide the same libraries).
I did not try the compt-glibc5, which was suggested in some forum (yet)
my ask: in the spirit of minimizing image size for k8s system - possible to change the snappy Java code
Having MUSL support built in will be a step forward to help deployments of snappy Java (we use it as part or parquet Java) - it willl eliminate lot of wasted time on runtime errors
The text was updated successfully, but these errors were encountered: