Multi-arch Mandrel image for Quarkus native build #12
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
solsson
added a commit
to Yolean/kafka-hook
that referenced
this pull request
Feb 19, 2022
|
On a small application like kafka-hook I get 90s build time for the native-image step on M1 Pro which is similar to what I get on a desktop Linux amd64. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Prior work:
We happen to be using Java 11 + Mandrel 22.0.0.2 on Ubuntu, so I found it easier to get the vanilla Mandrel distribution than to fork any of those. The https://github.com/quarkusio/quarkus-images Quarkus images use build infra that's very far from ours.
Emulation as in https://github.com/qiot-project/qiot-ubi-multiarch-builder is interesting, but given our current 10-15 minutes build time on the host's native platform I think the way forward is to use both amd64 and arm64 build nodes.