From ae50e3bf0dea66e75a70221b4a2e0c1f1c3d5f2a Mon Sep 17 00:00:00 2001 From: Robert Gogolok Date: Tue, 19 Nov 2024 10:00:53 +0100 Subject: [PATCH] Linux arm64 launcher required for Mac users (#788) When a Mac users exports the artifacts built by the `builder`, the `launcher` executable packaged into an OCI image must be linux arm64 in the tutorial. Signed-off-by: Robert Gogolok --- .../docs/for-platform-operators/tutorials/lifecycle/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/for-platform-operators/tutorials/lifecycle/_index.md b/content/docs/for-platform-operators/tutorials/lifecycle/_index.md index e1c728936..9975a06fe 100644 --- a/content/docs/for-platform-operators/tutorials/lifecycle/_index.md +++ b/content/docs/for-platform-operators/tutorials/lifecycle/_index.md @@ -42,7 +42,7 @@ Now that you’re set up, let’s build our `Bash` application and dive deeper i As a starting step, you need to build the `lifecycle` in order to use its phases. This could be done by navigating to the `lifecycle` directory and executing one of the following commands, depending on your system architecture. * `make build-linux-amd64` for `AMD64` architectures (for Linux users) -* `make build-darwin-arm64` for `ARM64` architectures (for Mac users) +* `make build-darwin-arm64 && make build-linux-arm64-launcher` for `ARM64` architectures (for Mac users) It's recommended to check the [lifecycle releases][releases] page to download binaries based on your system. > Please note that the entire process is most easily followed on Linux systems