Howto build x86_64 linux image on Apple Silicon machine

[sbeigel]

I need to run native images on x86_64 linux systems and want to build on my local machine but creating a native build with quarkus.native.container-build=true fails on my M3 Mac if I use a x86_64 container and set the arch to "x86-64-v2". The docker run command fails with a Java (Mandrel...) crash. I tried podman and colima -- same results.

Creating an ARM binary using an ARM container works as expected.

[quarkus-bot[bot]]

/cc @Karm (mandrel), @galderz (mandrel), @zakkak (mandrel)

[codespearhead]

Try starting the podman machine like this.

[sbeigel]

Thanks! I had found that article and already tried it though it is outdated. Using the lastest podman version, it doesn‘t work… I have not tried with an old (4.x) version but I prefer an up-to-date solution 😀

[maxandersen]

What's the errors you get ? And where/how do you set the arch?

[sbeigel]

colima start --vm-type=vz --vz-rosetta --cpu 10 --memory 24 --arch x86_64

quarkus create app com.acme:native-test

cd native-test

quarkus.native.additional-build-args=-march=x86-64-v2

echo quarkus.native.additional-build-args=-march=x86-64-v2 >> src/main/resources/application.properties

quarkus build --native --no-tests -Dquarkus.native.container-build=true

Output:

[...]
[INFO] [io.quarkus.deployment.pkg.steps.JarResultBuildStep] Building native image source jar: /path/to/native-test/target/native-test-1.0.0-SNAPSHOT-native-image-source-jar/native-test-1.0.0-SNAPSHOT-runner.jar
[INFO] [io.quarkus.deployment.pkg.steps.NativeImageBuildStep] Building native image from /path/to/native-test/target/native-test-1.0.0-SNAPSHOT-native-image-source-jar/native-test-1.0.0-SNAPSHOT-runner.jar
[INFO] [io.quarkus.deployment.pkg.steps.NativeImageBuildContainerRunner] Using docker to run the native image builder
[INFO] [io.quarkus.deployment.pkg.steps.NativeImageBuildContainerRunner] Pulling builder image 'quay.io/quarkus/ubi-quarkus-mandrel-builder-image:jdk-21'
jdk-21: Pulling from quarkus/ubi-quarkus-mandrel-builder-image
Digest: sha256:2fa929894b1e87d466236c889e169810d8cf9a29f393c5d5d2af61ce245a743f
Status: Image is up to date for quay.io/quarkus/ubi-quarkus-mandrel-builder-image:jdk-21
quay.io/quarkus/ubi-quarkus-mandrel-builder-image:jdk-21
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  7.879 s
[INFO] Finished at: 2024-03-26T08:26:51+01:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal io.quarkus.platform:quarkus-maven-plugin:3.8.3:build (default) on project native-test: Failed to build quarkus application: io.quarkus.builder.BuildException: Build failure: Build failed due to errors
[ERROR] 	[error]: Build step io.quarkus.deployment.pkg.steps.NativeImageBuildStep#build threw an exception: java.lang.RuntimeException: Failed to get GraalVM version
[ERROR] 	at io.quarkus.deployment.pkg.steps.NativeImageBuildRunner.getGraalVMVersion(NativeImageBuildRunner.java:40)
[ERROR] 	at io.quarkus.deployment.pkg.steps.NativeImageBuildStep.build(NativeImageBuildStep.java:217)
[ERROR] 	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[ERROR] 	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
[ERROR] 	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[ERROR] 	at java.base/java.lang.reflect.Method.invoke(Method.java:568)
[ERROR] 	at io.quarkus.deployment.ExtensionLoader$3.execute(ExtensionLoader.java:849)
[ERROR] 	at io.quarkus.builder.BuildContext.run(BuildContext.java:256)
[ERROR] 	at org.jboss.threads.ContextHandler$1.runWith(ContextHandler.java:18)
[ERROR] 	at org.jboss.threads.EnhancedQueueExecutor$Task.run(EnhancedQueueExecutor.java:2513)
[ERROR] 	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1538)
[ERROR] 	at java.base/java.lang.Thread.run(Thread.java:833)
[ERROR] 	at org.jboss.threads.JBossThread.run(JBossThread.java:501)
[ERROR] Caused by: java.lang.IllegalArgumentException: Cannot parse version from output: 
[ERROR] #
[ERROR] # A fatal error has been detected by the Java Runtime Environment:
[ERROR] #
[ERROR] #  SIGSEGV (0xb) at pc=0x00007f9ea08fdfc0, pid=1, tid=15
[ERROR] #
[ERROR] # JRE version: OpenJDK Runtime Environment Temurin-21.0.2+13 (21.0.2+13) (build 21.0.2+13-LTS)
[ERROR] # Java VM: OpenJDK 64-Bit Server VM Temurin-21.0.2+13 (21.0.2+13-LTS, mixed mode, tiered, jvmci, compressed oops, compressed class ptrs, g1 gc, linux-amd64)
[ERROR] # Problematic frame:
[ERROR] # J 191 c1 java.lang.String.substring(II)Ljava/lang/String; [email protected] (58 bytes) @ 0x00007f9ea08fdfc0 [0x00007f9ea08fdfa0+0x0000000000000020]
[ERROR] #
[ERROR] # Core dump will be written. Default location: /project/core
[ERROR] #
[ERROR] # An error report file with more information is saved as:
[ERROR] # /tmp/hs_err_pid1.log
[ERROR] [1.057s][warning][os] Loading hsdis library failed
[ERROR] #
[ERROR] # If you would like to submit a bug report, please visit:
[ERROR] #   https://github.com/adoptium/adoptium-support/issues
[ERROR] #
[ERROR] 
[ERROR] [error occurred during error reporting (), id 0xb, SIGSEGV (0xb) at pc=0x00007f9ebfb94f81]
[ERROR] 	at io.quarkus.deployment.pkg.steps.GraalVM$Version.of(GraalVM.java:311)
[ERROR] 	at io.quarkus.deployment.pkg.steps.NativeImageBuildRunner.getGraalVMVersion(NativeImageBuildRunner.java:37)
[ERROR] 	... 12 more
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

Even a simple "-march=list" fails with a crash:

docker run --env LANG=C --rm --user 501:20 -v /path/to/native-test/target/native-test-1.0.0-SNAPSHOT-native-image-source-jar:/project:z --name build-native-VzefK quay.io/quarkus/ubi-quarkus-mandrel-builder-image:jdk-21 -march=list

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGILL (0x4) at pc=0x00007f31388c1424, pid=1, tid=16
#
# JRE version: OpenJDK Runtime Environment Temurin-21.0.2+13 (21.0.2+13) (build 21.0.2+13-LTS)
# Java VM: OpenJDK 64-Bit Server VM Temurin-21.0.2+13 (21.0.2+13-LTS, mixed mode, tiered, jvmci, compressed oops, compressed class ptrs, g1 gc, linux-amd64)
# Problematic frame:
# J 16 c1 java.util.ImmutableCollections$SetN.probe(Ljava/lang/Object;)I [email protected] (56 bytes) @ 0x00007f31388c1424 [0x00007f31388c1400+0x0000000000000024]
#
# Core dump will be written. Default location: /project/core
#
# An error report file with more information is saved as:
# /project/hs_err_pid1.log
[1.238s][warning][os] Loading hsdis library failed
#
# If you would like to submit a bug report, please visit:
#   https://github.com/adoptium/adoptium-support/issues
#

[error occurred during error reporting (), id 0xb, SIGSEGV (0xb) at pc=0x00007f3157171f81]

[sbeigel]

OK, I think I got it working using podman 5.0.0 as it already supports multi platform, you have to provide that info as a flag, i.e. use "--platform linux/amd64" on the docker command:

docker run --platform linux/amd64 --env LANG=C --rm --user 501:20 -v /path/to/IdeaProjects/native-test/target/native-test-1.0.0-SNAPSHOT-native-image-source-jar:/project:z --name build-native-VzefK quay.io/quarkus/ubi-quarkus-mandrel-builder-image:jdk-21 -march=list

On AMD64, the following machine types are available:

'compatibility'
  CPU features: all of 'x86-64'
'haswell'
  CPU features: all of 'x86-64' + SSE3 + SSSE3 + SSE4_1 + SSE4_2 + POPCNT + LZCNT + AVX + AVX2 + AES + CLMUL + BMI1 + BMI2 + FMA
'native'
  CPU features: CX8 + CMOV + FXSR + MMX + AMD_3DNOW_PREFETCH + SSE + SSE2 + SSE3 + SSSE3 + SSE4A + SSE4_1 + SSE4_2 + POPCNT + LZCNT + TSC + AVX + AVX2 + AES + ERMS + CLMUL + BMI1 + BMI2 + ADX + FMA + VZEROUPPER + FLUSH + FLUSHOPT + HV + RDTSCP + RDPID + FSRM + F16C + PKU
'skylake'
  CPU features: all of 'haswell' + AMD_3DNOW_PREFETCH + ADX + FLUSHOPT
'skylake-avx512'
  CPU features: all of 'skylake' + AVX512F + AVX512DQ + AVX512CD + AVX512BW + AVX512VL + CLWB
'x86-64'
  CPU features: CX8 + CMOV + FXSR + MMX + SSE + SSE2
'x86-64-v1'
  CPU features: all of 'x86-64'
'x86-64-v2'
  CPU features: all of 'x86-64-v1' + SSE3 + SSSE3 + SSE4_1 + SSE4_2 + POPCNT
'x86-64-v3'
  CPU features: all of 'x86-64-v2' + LZCNT + AVX + AVX2 + BMI1 + BMI2 + FMA
'x86-64-v4'
  CPU features: all of 'x86-64-v3' + AVX512F + AVX512DQ + AVX512CD + AVX512BW + AVX512VL

I configured quarkus to use this option (tried both podman & docker), but it complains that it's unknown:

quarkus.native.container-runtime=podman
quarkus.native.container-runtime-options=--arch amd64

or

quarkus.native.container-runtime=docker
quarkus.native.container-runtime-options=--platform linux/amd64

podman run --env LANG=C --rm --user 501:20 --arch amd64 -v [...]

Error: unknown flag: --arch amd64
See 'podman run --help'
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[...]

But when I copy & paste the quarkus generated command and execute it manually, the flag gets recognized it it seems to work...

[codespearhead]

@sbeigel This could be a syntax problem. Try this:

quarkus/docs/src/main/asciidoc/virtual-threads.adoc

Lines 396 to 408 in 18d873e

	[IMPORTANT]
	.From ARM/64 to AMD/64
	====
	If you are using a Mac M1 or M2 (using an ARM64 CPU), you need to be aware that the native executable you will get using an in-container build will be a Linux executable, but using your host (ARM 64) architecture.
	You can use emulation to force the architecture when using Docker with the following property:
	[source, properties]
	----
	quarkus.native.container-runtime-options=--platform=linux/amd64
	----
	Be aware that it increases the compilation time... a lot (>10 minutes).
	====

[sbeigel]

Thanks, indeed, adding the "=" works:

quarkus.native.container-runtime-options=--arch=amd64

or

quarkus.native.container-runtime-options=--platform=linux/amd64

To be honest, this looks like a "bug" to me, as the quarkus generated and printed docker or podman command works perfectly fine without the "=" if you copy and execute by hand. It should at least be made VERY clear in the docs and maybe even in the error message, that you have to add it.

[codespearhead]

@sbeigel I’ve created issue #39808 to track this bug.

Can you mark my previous response as the answer to this discussion?