Spring Boot Admin GraalVM sample application

This is a sample project running a Spring Boot Admin server which works with GraalVM and Native Image Builder.

In order to show basic functionalities, the server itself is registered as a client.

Build project

Make sure to use a GraalVM with a v17-BaseJDK to build the project (e.g. GraalVM Oracle 17.0.8). If you're using sdkman:

sdk install java 17.0.8-graal

Build the application with the native profile:

mvn -Pnative native:compile

The native application will now be build in the target folder.

cd target
./spring-boot-admin-sample-servlet-graalvm

You should now be able to access Spring Boot Admin locally under http://localhost:8080/

Build an OCI image that can be run with Docker

mvn spring-boot:build-image -Pnative -Dspring-boot.build-image.imageName=spring-boot-admin-sample-servlet-graalvm:latest

Depending on your OS, you might want to change the builder in your pom.xml.

Right now, <builder>dashaun/native-builder:focal-arm64</builder> is a good choice for ARM64.

In most other cases <builder>paketobuildpacks/builder:tiny</builder> should do the job.

Running the example

docker run --rm -p 8080:8080 docker.io/library/spring-boot-admin-sample-servlet-graalvm:latest

You should now be able to access Spring Boot Admin locally under http://localhost:8080/

Current limitations of Spring Boot's native image build feature

Keep in mind that currently not all Spring modules have built-in support. Therefore, you might need to tell the AOT compiler about the usage of reflection, dynamic proxies etc. There are several ways to deal with these concerns. A good starting point for specifying additional native configuration can be found in the official Spring documentation. Some features like gc and memory metrics are not supported by GraalVM yet. So some views (e.g. gc-details) are currently not working.