[BUG] bb commands run slow, when running under M1 MacOS

[FieryCod]

[BUG] bb commands run slow, when running under M1 MacOS

[FieryCod]

Making M1 work fine with HL or any other "native" (applies to compiled ones like golang, rust, c++) is hard. That's because AWS Lambda requires Linux amd64 binary. Producing valid binary for compiled languages is done by using Docker with a Linux Amazon Image. The build time of such binary on Docker varies across the different OSes and architectures. For M1, it's painfully slow and very likely that the build process will hang, which is the result of the early stage of Docker amd64 emulation on M1.

While there is an option to make some of the HL commands run fast on M1 by leveraging aarch64 Linux image, it's impossible to run the native-compiled aarch64 binary on AWS Lambda. AWS Lambda will hardly ever support aarch64, and that's why I've asked the question on GraalVM slack whether it's possible to cross-compile on aarch64 to amd64. While certainly, it's possible the GraalVM team may likely not introduce the following change soon.

For now, M1 users should believe that Docker is going to fix the emulation for amd64.

Recommended workarounds for now:

• VNC + Oracle Cloud
• VNC + AWS
• AWS + Cloud9 https://aws.amazon.com/cloud9/

[FieryCod]

Since 0.6.0 version users with M1 should use ghcr.io/fierycod/holy-lambda-builder:aarch64-java11-21.3.0 or any alternative aarch64 builder available here and target ARM64 Lambda Architecture.

ARM64 is actually much better for Lambda, therefore I recommend it for all the users. See here

[FieryCod]

Fixed in 0.6.0

EDIT: cc @stevebuik