-
Notifications
You must be signed in to change notification settings - Fork 446
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
GraalVMNativeImagePlugin produces broken docker images without native-image in the PATH #1492
Comments
And here is a quick monkeypatch:
|
Thanks a lot @pshirshov Could you explain what the issue is and open a PR? 😊👋 |
Yep
Well, in case the explanation I've added is not enough - probably I won't be able to explain better :( |
I think issue is related to graalvm image. With prior versions(prior to graalvm 22) gu install process creating a symbolic link(via alternatives i think) under /usr/bin but with version 22 it just install native-image binary under $JAVA_HOME/bin. |
I think it is as issue with all recently published graalvm images.i tried with 21.3.1 and failed again |
Would be nice to get this fix in soon since there is no manual workaround it affects updated graalvm images on old versions too. My only concern is that it locks the OS type to |
That's not the best possible solution, I guess it would be better to allow the user to override the |
You can already override it to use the I wrote it that way to keep using the baseline image (not sure how important that is really..). And I noticed that the |
Yes, but that's kinda painful. |
Try to enable
GraalVMNativeImagePlugin
on a project and setThis would produce a broken docker image:
The text was updated successfully, but these errors were encountered: