-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
native-image
parameters are not compatible after upgrade to the patch version 22.0.1
#8816
Comments
Hello @davinkevin For this version: |
@ZynoZin , I know, but should this be included in the docker image provided by the project? |
Hello @davinkevin , thank you for reaching out. Can you please check this image: |
Thank you for your answer. I just discover this new image, good to know. Using this image, and with PS: There is a strange error if Finally, you answered part of my request, you still think this breaking change in the cli "api" is not an issue for a patch release? |
No, this change was necessary because there was a bug when |
Thank you for the extra details. 👍 |
Describe the issue
We have the following
dockerfile
, using the official image with version22.0.0
:The build was working perfectly, with the following report:
Then, we have upgraded to the patch version
22.0.1
:And the result is different:
If we follow the error recommendation, "Remove the '--static' option or add the '--libc=musl'", we have the following error:
My expectation was to have everything setup and ready in the
native-image
docker image, it's the main reason we use it 😇.So the bug is mainly about the CLI parameters breaking change in a patch version, but other element can be considered (no
x86_64-linux-musl-gcc
in the imagefor example).
Describe GraalVM and your environment:
I tried to add as much information as possible, because everything is based on official images and code we build is just Java (no dependency nor framework),
I think it's not required to provide more data… but let me know if you need something else.
The text was updated successfully, but these errors were encountered: