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

arm64 native docker image does not work on kernel with 16K page size #1073

Closed
diegobfernandez opened this issue Nov 12, 2024 · 3 comments · Fixed by #1078
Closed

arm64 native docker image does not work on kernel with 16K page size #1073

diegobfernandez opened this issue Nov 12, 2024 · 3 comments · Fixed by #1078

Comments

@diegobfernandez
Copy link

diegobfernandez commented Nov 12, 2024

I am running elastimq-native in docker and the containers immediatly exits with error Failed to create main Isolate.
My computer is a arm64 apple silicon running Asahi Linux. I've faced this issue with babashka and other Clojure tools that rely on GraavlVM.

This is a recurrent issue with software built with GraalVM since it defaults to the kernel page size of the host running the build.

The solution is to build with 64K page size which is compatible with all other officially supported ARM page sizes.

Here is the solution I proposed for all graalvm packages in nixpkgs: NixOS/nixpkgs#269522.
Similar solution can be applied to build.sbt to allow usage in asahi linux and newer raspberry pi images.

This is an graalvm issue about this topic: oracle/graal#5605 (comment)

@micossow
Copy link
Contributor

Hi @diegobfernandez I created a branch with the param you suggested and it seems to built successfully. Can you verify if the image softwaremill/elasticmq-native:1.6.10-RC1 works on your hardware?

@diegobfernandez
Copy link
Author

Thanks a lot @micossow. I can confirm that softwaremill/elasticmq-native:1.6.10-RC1 works on Asahi's 16K page size Linux.
Unfortunately I won't be able to test it on my Raspberry PI 5 in the next couple of months, but from past experiences it should work 🤞

@micossow
Copy link
Contributor

Thanks! The fix has been released.

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