arm64 workflow: build via buildx/BuildKit sidecar #17
Loading…
Reference in a new issue
No description provided.
Delete branch "ci/arm64-buildx"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The self-hosted
macos-arm64runner (m1pro-mac) was migrated from a Homebrew host-modeact_runner(ran as the user, full host access) to an isolated container on OrbStack with no Docker daemon/socket — it builds through a rootless BuildKit sidecar (project:~/ci-runner).Consequence:
docker build/docker pushno longer work on this runner (they need a daemon). This updatesdocker-publish-arm64.ymlto:docker buildx build --platform linux/arm64 --push ...— builds via BuildKit and pushes all tags in one step, no daemon needed;PATHshim that only applied to the old host-mode runner (the container hasdocker/buildxon PATH).No functional change to what's published (same tags, same registry). Merging to
maintriggers the workflow, which serves as the end-to-end test of the new runner.Relates to #10 (arm64 image publishing).