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
[skip changelog] Use compatible runner for macOS Apple Silicon nightly builds (#3007)
The `docker.elastic.co/beats-dev/golang-crossbuild:1.24.4-darwin-arm64-debian10` container is used for the release
builds for the macOS Apple Silicon host. This container will only run on hosts of the linux/arm64 architecture.
The GitHub Actions runner machine previously used to perform the release builds is of the linux/amd64 architecture and
so is not compatible with the container. This caused the release builds to fail:
```
Status: Downloaded newer image for docker.elastic.co/beats-dev/golang-crossbuild:1.24.4-darwin-arm64-debian10
WARNING: The requested image's platform (linux/arm64/v8) does not match the detected host platform (linux/amd64/v3) and no specific platform was requested
exec /crossbuild: exec format error
task: Failed to run task "dist:macOS_ARM64": exit status 255
```
The failure is resolved by configuring the release workflows to use the `ubuntu-24.04-arm` runner machine that is
compatible with the container.
This was already done for the release and tester build workflows, but the fix was not applied to the nightly build
workflow at that time.
It is standard practice to use the "latest" GitHub Actions runner identifiers in the project's workflows, which causes
the workflow runs to always use the newest stable runner version. However, GitHub has broken from this established
convention by choosing to not provide "latest" identifiers for the Linux ARM runners. For this reason, the
version-specific runner name was used in the workflow. It will be necessary to manually update the runner name as new
stable versions are made available (or more likely after GitHub's removal of the runner in use breaks the workflows).
0 commit comments