-
Notifications
You must be signed in to change notification settings - Fork 16
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
Add GraalVM support #103
Comments
Progress
I used sdkman to install Graal 19.3.0. Then I installed the
After building a
I attempted to build a native image with:
Result
Action Items
|
With the recent release of Graal 19.3.1 I decided to give the native image build another try but was sorely disappointed
yielded
Need to dig into this a bit more. |
Still seeing the same exception as noted earlier with |
So there's this project, spring-graal-native and this guidance. tl;dr Have fire up the app with java and the agent, exercise code paths, then use the configuration data when building the native image. Not 100% guarantee this'll work though. Will report back later. |
An updated release of Spring Graal Native is available, but perhaps a bit too involved to confidently generate a functioning native-image. |
Getting close now. The codebase has been brought forward to Spring Boot 2.4.0.M2. So we'll be in position to produce native images using the Maven plugin. Unfortunately, it appears we're hung up on JGit support in GraalVM, see https://bugs.eclipse.org/bugs/show_bug.cgi?id=546175. And it even looks like there's an outstanding PR that potentially addresses it, here: https://github.com/eclipse/jgit/pull/65. |
So, latest testing with Spring Boot 2.4.5 and Spring Native 0.9.2 yielded exceptions (see below). Seems to point to an issue w/ Log4J2 and LMAX Disruptor dependencies now. I chose that combo for logging purposes early on because Logback drops messages.
|
Some great progress by the Spring engineering team on features and fixes within spring-native. Latest trial here, allows for successful build of container image with
but when we attempt to run with
we see
It wasn't immediately evident what was the matter above, until I scoured the issues backlog and saw that there is no support for EventListeners yet. Hopefully we'll see support soon in the spring-native 0.11.x release branch. Current effort can be tracked in native-hints-scan-feature branch. |
While we have Graal native image compilation plumbed, the images produced lack certain resources at runtime. We have some variability at build time in terms of which
|
Recently adjusted config for
|
Unfortunately, cf-butler makes use of some Java 11 features. Turns out there's an open issue logged here. As soon as this is resolved, and we have a new release of GraalVM, I'll give this a try.
The text was updated successfully, but these errors were encountered: