ARM 64 Docker Image Builds broken since 2.6x

Describe the bug

While Quarkus is sadly still missing, support for building ARM64 Images. This could be relatively simply fixed by suppling your own builder image, e.g.:

<quarkus.native.builder-image>goafabric/quarkus-build-aarch64:java11-21.3.0</quarkus.native.builder-image>

While this worked perfectly fine until 2.5.3, it’s now broken since 2.6x.

The build process puts out a warning that the final Image will be AMD64 and not ARM64.

Judging from another bug report here, there seems to be a change in the Base Images, Quarkus supplies. It seems that this was multi-arch before and now seems to be solely AMD64.

The Container will of course then crash during bootstrap.

Expected behavior

Bug is fixed, to be able to use the workaround again. Or direct support form ARM64 Images is implemented

Actual behavior

Wrong Baseimage is used, Application crashes

How to Reproduce?

No response

Output of uname -a or ver

Darwin MacBook-Air-von-Andreas.local 21.2.0 Darwin Kernel Version 21.2.0: Sun Nov 28 20:29:10 PST 2021; root:xnu-8019.61.5~1/RELEASE_ARM64_T8101 arm64

Output of java -version

openjdk version “11.0.10” 2021-01-19 LTS

GraalVM version (if different from Java)

No response

Quarkus version or git rev

2.6.2

Build tool (ie. output of mvnw --version or gradlew --version)

maven

Additional information

No response

[cescoffier]

Reading other comments, it’s quay.io/quarkus/quarkus-micro-image which is not multi-arch. We can (must) definitely fix this.

[cescoffier]

@goafabric I just looked at the image we currently use:

• ubi8/openjdk-17 : https://catalog.redhat.com/software/containers/ubi8/openjdk-17/618bdbf34ae3739687568813
• ubi/openjdk-11: https://catalog.redhat.com/software/containers/ubi8/openjdk-11/5dd6a4b45a13461646f677f4

I inspected their manifests and they are both multi-architectures:

• amd64
• arm64
• ppc64le
• s390x

So, it should not be a problem.