이 섹션에서는 GraalVM의 네이티브 이미지 빌더를 사용하여 Spring Boot 애플리케이션에서 네이티브 이미지를 생성하는 방법과 이 네이티브 이미지를 Docker 컨테이너에서 실행하는 방법을 설명합니다.
소프트웨어 아키텍처와 마이크로서비스 아키텍처 설계에서는 애플리케이션의 확장성과 성능을 고려해야 합니다. 우리 애플리케이션은 요청 수가 증가할 때마다 신속하게 확장을 시작하고 리소스를 효율적으로 활용해야 합니다.
GraalVM과 함께 AOT(Spring Boot Ahead of Time) 컴파일을 사용하여 Java 가상 스레드(JDK 21 이상에서 사용 가능)와 함께 컨테이너에서 실행 파일을 실행하는 것을 고려하고 있습니다.
이 아키텍처 설계 결정에서는 이점을 얻지만 다음 구현 과제와 설계 고려 사항도 고려해야 합니다.
Spring Boot 애플리케이션
이 사용 사례를 테스트하기 위해 "/hello"에 REST 끝점을 노출하는 Spring Boot 애플리케이션을 구축하고 있습니다. 저는 다음 구성, 라이브러리 및 도구를 사용하고 있습니다.
POM XML 파일에 다음 구성을 추가해야 합니다.
Spring Boot 속성 구성
<properties> <java.version>22</java.version> <spring-native.version>0.12.1</spring-native.version> </properties>
Spring Boot AOT 플러그인 구성
<plugin> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-maven-plugin</artifactId> <executions> <execution> <id>process-aot</id> <goals> <goal>process-aot</goal> </goals> </execution> </executions> </plugin>
GraalVM 플러그인 구성
<plugin> <groupId>org.graalvm.buildtools</groupId> <artifactId>native-maven-plugin</artifactId> <configuration> <imageName>app-native-binary</imageName> <metadataRepository> <enabled>true</enabled> </metadataRepository> <buildArgs> <buildArg>--static --libc=musl</buildArg> <buildArg>-H:+ReportExceptionStackTraces</buildArg> </buildArgs> <mainClass>com.developerhelperhub.tutorial.springboot.tutorial.TutorialStartupPerformanceApplication</mainClass> </configuration> <executions> <execution> <id>add-reachability-metadata</id> <goals> <goal>add-reachability-metadata</goal> </goals> </execution> </executions> </plugin>
컨테이너 내에서 네이티브 이미지가 실행될 특정 OS 호스트 및 CPU 아키텍처에 대한 네이티브 이미지를 빌드해야 합니다.
우리는 컨테이너에서 애플리케이션을 실행하기 위해 작은 크기, 단순성 및 보안을 위해 Alpine Linux를 사용하고 있습니다. 이를 달성하려면 애플리케이션 구축에 적합한 GraalVM 구성을 사용해야 합니다. Alpine의 시스템 요구 사항은 운영 체제와 CPU 아키텍처입니다.
다음 명령을 사용하여 "amd64/alpine" 이미지를 검사할 수 있습니다
docker pull amd64/alpine # pull the image docker image inspect amd64/alpine # inspect the image
We can use docker container to build the native image instead of setup the GraalVM and Java related configuration in our locally. I am using “ghcr.io/graalvm/native-image-community:22-muslib” docker image to build the native.
Following command we can use to inspect the “ghcr.io/graalvm/native-image-community:22-muslib” image
docker pull ghcr.io/graalvm/native-image-community:22-muslib # pull the image docker image inspect ghcr.io/graalvm/native-image-community:22-muslib # inspect the image
I am creating a build image to test and debug the container, ensuring that all configurations and services are installed correctly. This approach will help us quickly identify and resolve any issues.
Following steps are added in the docker file, the file name “DockerfileBuild”
FROM ghcr.io/graalvm/native-image-community:22-muslib as build # Install necessary tools RUN microdnf install wget RUN microdnf install xz # Install maven for build the spring boot application RUN wget https://dlcdn.apache.org/maven/maven-3/3.9.8/binaries/apache-maven-3.9.8-bin.tar.gz RUN tar xvf apache-maven-3.9.8-bin.tar.gz # Set up the environment variables needed to run the Maven command. ENV M2_HOME=/app/apache-maven-3.9.8 ENV M2=$M2_HOME/bin ENV PATH=$M2:$PATH # Install UPX (Ultimate Packer for eXecutables) to compress the executable binary and reduce its size. RUN wget https://github.com/upx/upx/releases/download/v4.2.4/upx-4.2.4-amd64_linux.tar.xz RUN tar xvf upx-4.2.4-amd64_linux.tar.xz # Set up the environment variables required to run the UPX command. ENV UPX_HOME=/app/upx-4.2.4-amd64_linux ENV PATH=$UPX_HOME:$PATH #Copy the spring boot source code into container RUN mkdir -p /app/spring-boot-rest-api-app COPY spring-boot-rest-api-app /app/spring-boot-rest-api-app #Compile the native image RUN cd /app/spring-boot-rest-api-app && mvn -Pnative native:compile #Compressed binary file RUN upx -7 -k /app/spring-boot-rest-api-app/target/app-native-binary WORKDIR /app ENTRYPOINT ["/bin/bash"]
I am using the UPX compression tool in the build process to reduce the image size, UPX will typically reduce the file size of programs and DLLs by around 50%-70%, thus reducing disk space, network load times, download times and other distribution and storage costs.
Use the following command to build the Docker image.
docker build --no-cache -f DockerfileBuild -t alpine-graalvm-build .
After the build is complete, the image size will be 1.85 GB.
REPOSITORY TAG IMAGE ID CREATED SIZE alpine-graalvm-build latest 81d23bc1bc99 36 seconds ago 1.85GB
We can verify the configuration and installation within the container before creating a smaller container inside the Alpine Linux box. The following command will allow us to enter the container:
docker run --rm -it --entrypoint /bin/bash alpine-graalvm-build java --version #verify the java version mvn --version #verify the maven version upx --version #verify the upx version ls /app/spring-boot-rest-api-app/target/app-native-binary #verify the binary available /app/spring-boot-rest-api-app/target/app-native-binary #run the executable
We know that this native image includes all the dependencies necessary to run the binary standalone, without requiring any build-related tools such as GraalVM, Maven, UPX, or source code. We can use a Docker multi-stage build approach to copy the build file into our application image. By using multiple stages, you can separate the build environment from the runtime environment. This means only the necessary artifacts are included in the final image, significantly reducing its size.
Following steps are added in the docker file, the file name “DockerfileBuildAndCreateAlpineContainer”
FROM ghcr.io/graalvm/native-image-community:22-muslib as build # Install necessary tools RUN microdnf install wget RUN microdnf install xz # Install maven for build the spring boot application RUN wget https://dlcdn.apache.org/maven/maven-3/3.9.8/binaries/apache-maven-3.9.8-bin.tar.gz RUN tar xvf apache-maven-3.9.8-bin.tar.gz # Set up the environment variables needed to run the Maven command. ENV M2_HOME=/app/apache-maven-3.9.8 ENV M2=$M2_HOME/bin ENV PATH=$M2:$PATH # Install UPX (Ultimate Packer for eXecutables) to compress the executable binary and reduce its size. RUN wget https://github.com/upx/upx/releases/download/v4.2.4/upx-4.2.4-amd64_linux.tar.xz RUN tar xvf upx-4.2.4-amd64_linux.tar.xz # Set up the environment variables required to run the UPX command. ENV UPX_HOME=/app/upx-4.2.4-amd64_linux ENV PATH=$UPX_HOME:$PATH #Copy the spring boot source code into container RUN mkdir -p /app/spring-boot-rest-api-app COPY spring-boot-rest-api-app /app/spring-boot-rest-api-app #Compile the native image RUN cd /app/spring-boot-rest-api-app && mvn -Pnative native:compile #Compressed binary file RUN upx -7 -k /app/spring-boot-rest-api-app/target/app-native-binary WORKDIR /app #Second stage: Create the runtime image FROM amd64/alpine #Set the working directory WORKDIR /app #Copy the built application from the first stage COPY --from=build /app/spring-boot-rest-api-app/target/app-native-binary . #Expose port which our spring boot application is running EXPOSE 8080 #Command to run the application ENTRYPOINT ["/app/app-native-binary"]
Use the following command to build the Docker image.
docker build -f DockerfileBuildAndCreateAlpineContainer -t alpine-graalvm .
After the build is complete, the image size of container will be 32.8MB.
REPOSITORY TAG IMAGE ID CREATED SIZE alpine-graalvm latest 79676c696920 11 seconds ago 32.8MB
We can verify the container.
docker run --rm -it --entrypoint sh alpine-graalvm ls /app #verify the binary available /app/app-native-binary #run the executable
The application startup time is just 0.074 seconds, whereas a typical Spring Boot application running on the JVM has a startup time of approximately 1.665 seconds.
Started TutorialStartupPerformanceApplication in 0.074 seconds (process running for 0.075)
Following command can be use to run the docker container for running the application
docker run -d --name test-app -p 8080:8080 alpine-graalvm #run the container curl http://localhost:8080/hello # checking the endpoints
위 내용은 GraalVM 빌더를 사용하여 Spring Boot 애플리케이션에서 네이티브 이미지 빌드의 상세 내용입니다. 자세한 내용은 PHP 중국어 웹사이트의 기타 관련 기사를 참조하세요!