You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we offer a Forest image for linux/amd64, which should work on Mac M1, provided certain virtualization prerequisites are installed and configured. This may get a bit messy, and the out-of-the-box experience for the user should be better than that.
This can be done easily with QEMU; unfortunately, the cross-compilation duration using this utility is way too slow - around 30-40 minutes using the best buildjet worker. A native build (as suggested by @elmattic, thanks) on a regular machine takes only 10 minutes.
It would be fantastic to do two native builds, one for amd64 and another for arm64 and end up with a single, multi-platform image. The alternative is to have multiple tags and achieve multi-platform capacity this way, e.g. latest-arm, v0.6.0-arm. Easy to implement, but not the best experience we can offer.
Other information and links
A failed attempt can be found here #2475. In the end, I managed to produce a working native image for M1, but it's far from a perfect solution.
The text was updated successfully, but these errors were encountered:
Issue summary
Currently, we offer a Forest image for
linux/amd64
, which should work on Mac M1, provided certain virtualization prerequisites are installed and configured. This may get a bit messy, and the out-of-the-box experience for the user should be better than that.This can be done easily with QEMU; unfortunately, the cross-compilation duration using this utility is way too slow - around 30-40 minutes using the best buildjet worker. A native build (as suggested by @elmattic, thanks) on a regular machine takes only 10 minutes.
It would be fantastic to do two native builds, one for
amd64
and another forarm64
and end up with a single, multi-platform image. The alternative is to have multiple tags and achieve multi-platform capacity this way, e.g.latest-arm
,v0.6.0-arm
. Easy to implement, but not the best experience we can offer.Other information and links
A failed attempt can be found here #2475. In the end, I managed to produce a working native image for M1, but it's far from a perfect solution.
The text was updated successfully, but these errors were encountered: