From f176fbbf45ed607353a3875f51e136118e1e470f Mon Sep 17 00:00:00 2001 From: Stef <122795374+stefvanderweldevolksbanknl@users.noreply.github.com> Date: Tue, 22 Oct 2024 15:18:24 +0200 Subject: [PATCH 1/3] #44019 add note for lambda x86-64v2 compatibility --- docs/src/main/asciidoc/aws-lambda-http.adoc | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/src/main/asciidoc/aws-lambda-http.adoc b/docs/src/main/asciidoc/aws-lambda-http.adoc index 158eaefd97739..0b9dcbc24df41 100644 --- a/docs/src/main/asciidoc/aws-lambda-http.adoc +++ b/docs/src/main/asciidoc/aws-lambda-http.adoc @@ -88,6 +88,12 @@ NOTE: If you are building on a non-Linux system, you will need to also pass in a Lambda requires Linux binaries. You can do this by passing `-Dquarkus.native.container-build=true` to your build command. This requires you to have Docker installed locally, however. +NOTE: According to https://docs.aws.amazon.com/linux/al2023/ug/system-requirements.html#system-requirements-cpu-x86-64[the AWS docs], AL2023 +x86-64 binaries are built for the x86-64**v2** revision of the x86-64 architecture. Quarkus defaults +https://quarkus.io/guides/building-native-image#quarkus-core_quarkus-native-march[quarkus.native.march] to x86-64**v3**. This could cause +https://repost.aws/questions/QUBVnl6hn-Toe1LPr1qjOXzg/lambda-failed-with-java-compiled-into-machine-code[issues] if Lambda provisions older +hardware. To maximize Lambda compatibility, set `quarkus.native.march=x86-64v2`. + include::{includes}/devtools/build-native-container.adoc[] == Extra Build Generated Files From a0602854bbe42b1316599e58c72f10453b31fc65 Mon Sep 17 00:00:00 2001 From: Stef <122795374+stefvanderweldevolksbanknl@users.noreply.github.com> Date: Tue, 22 Oct 2024 14:19:33 +0000 Subject: [PATCH 2/3] #44019 add additional information about quarkus.native.march --- docs/src/main/asciidoc/aws-lambda-http.adoc | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/src/main/asciidoc/aws-lambda-http.adoc b/docs/src/main/asciidoc/aws-lambda-http.adoc index 0b9dcbc24df41..62b06033a3b1f 100644 --- a/docs/src/main/asciidoc/aws-lambda-http.adoc +++ b/docs/src/main/asciidoc/aws-lambda-http.adoc @@ -92,7 +92,8 @@ NOTE: According to https://docs.aws.amazon.com/linux/al2023/ug/system-requiremen x86-64 binaries are built for the x86-64**v2** revision of the x86-64 architecture. Quarkus defaults https://quarkus.io/guides/building-native-image#quarkus-core_quarkus-native-march[quarkus.native.march] to x86-64**v3**. This could cause https://repost.aws/questions/QUBVnl6hn-Toe1LPr1qjOXzg/lambda-failed-with-java-compiled-into-machine-code[issues] if Lambda provisions older -hardware. To maximize Lambda compatibility, set `quarkus.native.march=x86-64v2`. +hardware. To maximize Lambda compatibility, set `quarkus.native.march=x86-64v2` for x86-64. See: +https://quarkus.io/guides/native-reference#work-around-missing-cpu-features[] include::{includes}/devtools/build-native-container.adoc[] From 3ccb47e4ff17b60c7e01f2ba922357c19bca15ff Mon Sep 17 00:00:00 2001 From: Stef <122795374+stefvanderweldevolksbanknl@users.noreply.github.com> Date: Tue, 22 Oct 2024 14:43:19 +0000 Subject: [PATCH 3/3] #44019 fix typo --- docs/src/main/asciidoc/aws-lambda-http.adoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/src/main/asciidoc/aws-lambda-http.adoc b/docs/src/main/asciidoc/aws-lambda-http.adoc index 62b06033a3b1f..ca95eb926f4f7 100644 --- a/docs/src/main/asciidoc/aws-lambda-http.adoc +++ b/docs/src/main/asciidoc/aws-lambda-http.adoc @@ -89,10 +89,10 @@ Lambda requires Linux binaries. You can do this by passing `-Dquarkus.native.co This requires you to have Docker installed locally, however. NOTE: According to https://docs.aws.amazon.com/linux/al2023/ug/system-requirements.html#system-requirements-cpu-x86-64[the AWS docs], AL2023 -x86-64 binaries are built for the x86-64**v2** revision of the x86-64 architecture. Quarkus defaults -https://quarkus.io/guides/building-native-image#quarkus-core_quarkus-native-march[quarkus.native.march] to x86-64**v3**. This could cause +x86-64 binaries are built for the x86-64-**v2** revision of the x86-64 architecture. Quarkus defaults +https://quarkus.io/guides/building-native-image#quarkus-core_quarkus-native-march[quarkus.native.march] to x86-64-**v3**. This could cause https://repost.aws/questions/QUBVnl6hn-Toe1LPr1qjOXzg/lambda-failed-with-java-compiled-into-machine-code[issues] if Lambda provisions older -hardware. To maximize Lambda compatibility, set `quarkus.native.march=x86-64v2` for x86-64. See: +hardware. To maximize Lambda compatibility, set `quarkus.native.march=x86-64-v2` for x86-64. See: https://quarkus.io/guides/native-reference#work-around-missing-cpu-features[] include::{includes}/devtools/build-native-container.adoc[]