1 個回答
- 最新
- 最多得票
- 最多評論
-1
If this is happening with Graalvm Java 17, try Graalvm Java 21. Also, try switching the Java versions in the Lambda to match this.
已回答 3 個月前
相關內容
- 已提問 7 個月前
- AWS 官方已更新 3 年前
If this is happening with Graalvm Java 17, try Graalvm Java 21. Also, try switching the Java versions in the Lambda to match this.
I am not sure that helps. After a bit of digging, this error could mean the deployed image is built with newer version of CPU architecture (with new CPU instructions); and I believe the issue is the lambda is deployed with old CPU architecture which does not have these instruction support.
Ref: https://github.com/quarkusio/quarkus/wiki/Migration-Guide-3.2#native-compilation---work-around-missing-cpu-features
I recon' the fix is to apply "-march=compatibility" option, instruct Graalvm to compile image with backwards-compatibility