Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using snappy with MUSL #616

Open
yairlenga opened this issue Nov 10, 2024 · 1 comment · May be fixed by #632
Open

Using snappy with MUSL #616

yairlenga opened this issue Nov 10, 2024 · 1 comment · May be fixed by #632

Comments

@yairlenga
Copy link

yairlenga commented Nov 10, 2024

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

  1. Bundle a native build of snappy against MUSL library (in addition to the glibc build)
  2. Bundle the musl based code library into the jar file
  3. 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

@samyuh samyuh linked a pull request Jan 16, 2025 that will close this issue
@samyuh
Copy link

samyuh commented Jan 18, 2025

I'm going through the same issues when running snappy with Musl. I created a PR to fix this issue, please take a look and suggest updates if you want :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants