-
Notifications
You must be signed in to change notification settings - Fork 236
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
adoptopenjdk/openjdk11:alpine-jre fontconfig Segfault #520
Comments
Could be related to #517, will try installing freetype Edit: no luck, same error |
@mjp91 I was running into similar issues when my alpine-slim base image updated from using Alpine 3.12 to 3.13 yesterday. I reverted to an older tag that uses Alpine 3.12 and the segfaults aren't happening anymore. This one from the previous release before the most recent release should still work without segfaults https://hub.docker.com/layers/adoptopenjdk/openjdk11/x86_64-alpine-jre-11.0.9.1_1/images/sha256-961d26d00378688d5dd6bd4e00859f8fc9faaf33e2bf3cd528db8306e778287f?context=explore |
I can confirm that $ docker run -it adoptopenjdk/openjdk11:jre-11.0.10_9-alpine
/ # cat /etc/*release*
3.13.2
NAME="Alpine Linux"
ID=alpine
VERSION_ID=3.13.2
PRETTY_NAME="Alpine Linux v3.13"
HOME_URL="https://alpinelinux.org/"
BUG_REPORT_URL="https://bugs.alpinelinux.org/ I noticed it because I get the exact same
|
AdoptOpenJDK 11 is built against glibc. Alpine runs on musl libc and all libraries shipped with it do so, too. So if you blindly install any library that AdoptOpenJDK might need via apk, you're doing it wrong.
As you can see, when running FontTest, musl libc is being loaded ( Obviously, we have to fix the container images with Alpine and glibc. In the meantime, get the following packages:
Verify their signatures, unpack them, and copy all libraries with And a newer glibc is needed, too: https://github.com/sgerrand/alpine-pkg-glibc/releases/tag/2.33-r0. After Thankfully, AdoptOpenJDK 16 with musl support is around the corner and then those shenanigans aren't needed anymore. |
@dinogun @bharathappali Looking through the errors reported in other linked issues, the problem seems not to be limited to font support. Cubxity/docker-minecraft-server#1 (comment) has problems with network code. Might be worthwhile to undo the Alpine upgrade until one of you can figure out what the real problem is. |
I'm having this issue when a Java application is reading YAML files since this update, consistent segfaults. Version downgrade would be appreciated. I've switched to Amazon Corretto's docker image for now which has resolved my issue. |
@mjp91 Can I know if there is a specific test or program you tried to recreate the issue ? |
@bharathappali The FontTest @aahlenst did appears to produce the same error but I can roll up something specific if needed? Originated in a commercial app that uses JasperSoft reporting. |
@bharathappali https://blog.adoptopenjdk.net/2021/01/prerequisites-for-font-support-in-adoptopenjdk/ contains FontTest and is our generic program to checking for font issues. I'm more worried about what @clrxbl mentioned (reading YAML files and other things). |
Getting the same crash here since rebuiding our alpine base image.
|
I'm getting a core dump while building OpenJ9 image (OpenJ9 image has SCC generation phase which runs tomcat to generate SCC for base classes)
The issue got resolved after following the workaround provided by @aahlenst Updating GLIBC patch to 2.33 solved the issue.
|
I'm getting the same errors too for use fontconfig in adoptopenjdk jre alpine!
|
New images are over at github.com/adoptium/containers |
Seems to have been introduced in a recent update to base Alpine image (3.13).
Are there any older tags available so we can revert back to 3.12 or do I need to build my own image?
The text was updated successfully, but these errors were encountered: