Closed bodiam closed 1 month ago
When I say I had no issue, I spoke too soon: when I run my image using the following command: docker run --rm -p 8080:8080 docker.io/library/native:0.0.1-SNAPSHOT
I'm getting this error:
qemu-x86_64: Could not open '/lib64/ld-linux-x86-64.so.2': No such file or directory
This seems to be related to the buildpack?
Hi @bodiam,
Thank you for reaching out to us!
To help isolate the issue and confirm whether it is related to GraalVM or not, I followed the steps you provided and ensured that GraalVM was installed and properly configured on my machine. You can download the latest version from here.
Afterward, I ran the command ./gradlew nativeCompile
to build the native image and then I ran it and it completed successfully without any issues. Based on this, the problem you're encountering may be related to Docker rather than GraalVM. I suggest reaching out to the Docker support team to further investigate this.
Hi @selhagani , I think this is related to the Docker build images, they seem to not like ARM processors. I can confirm the nativeCompile
command works fine. Thanks for your time on this!
Describe the Issue
I'm building a Kotlin hello world Spring Boot app (see attached). It's created using start.spring.io, using only the web and native dependencies.
When I run
./gradlew bootBuildImage
, I'm getting a failed build.native 2.zip
Using the latest version of GraalVM can resolve many issues.
GraalVM Version
I'm not entirely sure, I'm using the buildPacks
Operating System and Version
MacOS
Build Command
./gradlew bootBuildImage
Expected Behavior
Successful build
Actual Behavior
Starting a Gradle Daemon, 1 incompatible Daemon could not be reused, use --status for details
FAILURE: Build failed with an exception.
What went wrong: Execution failed for task ':bootBuildImage'.
Try:
BUILD FAILED in 4m 34s 10 actionable tasks: 4 executed, 6 up-to-date
Steps to Reproduce
Additional Context
I've attempted it again for a second time, and the second time I ran
./gradlew bootBuildImage
, I had no issue, and the application compiled successfully.Build Log Output and Error Messages
No response