dave porter

I see the same thing. Alpine 3.17, adoptium openjdk jre 11.0.18 for x86_64, plus your alpine glibc 2.35-r1 (or r0). The JVM won't start - two undefined symbols in libjli.so....

If you're asking me, then it is as I said.... > Re-pointing /lib64/ld-linux-x86-64.so.2 to /usr/glibc-compat/lib/ld-linux-x86-64.so.2 fixes the problem, but I don't know what the side effects might be.

I just got back to looking at this for my own use-case. I tried adding this to the APKBUILD file: ``` mkdir -p "$pkgdir/lib64" ln -sf /usr/glibc-compat/lib64/ld-linux-x86-64.so.2 ${pkgdir}/lib64/ld-linux-x86-64.so.2 ``` Alas,...

I ran into a similar error in different circumstances. I was running an image based on the prebuilt eclipse-temurin docker image, plus alpine-pkg-glibc (2.3x, any available x), and homebrew Java...

> I am facing issues Everyone is.

Do you really have JKS content? The "Java Key Store" object (in Java) can deal with JKS or PKCS#12 content. The default from keytool is now to generate PKCS#12 material....