CI: stop pinning moby/buildkit:master in publish (regressed /proc/acpi)#10
Merged
Conversation
The publish workflow's two setup-buildx-action steps (build and build-arch) pinned the floating moby/buildkit:master. A recent master regressed on the rehosting-arc runners: runc run failed: ... can't mask dir "/proc/acpi": mount ... MS_RDONLY, data=nr_blocks=1,nr_inodes=1: invalid argument which fails the first RUN of every build. publish last succeeded 2026-04-15 on an older master and broke on the #9 merge run. Drop the image override so buildx uses its default pinned-stable buildkit (same fix already applied to build.yml).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The publish run on
mainafter #9 merged failed (run):It fails the first
RUNof every build, so nothing publishes. This is not related to the #9 Dockerfile change —publish.yml's twosetup-buildx-actionsteps (jobsbuildandbuild-arch) pin the floatingmoby/buildkit:master, and a recent master regressed on therehosting-arcrunners (runc/kernel interaction masking/proc/acpi). publish last succeeded 2026-04-15 on an older master and has been latently broken since.Fix
Drop the
image=moby/buildkit:masteroverride from both buildx setups so buildx uses its default pinned-stable buildkit (network=hostand the insecure-registry config are kept). This is the same fix already merged for the PR check inbuild.yml(#9), where it took the build from failing to green in ~4 min.Verification
The identical change on
build.yml(PR check, same runners, same proxy/cache setup) now builds thefinaltarget successfully onrehosting-arc. This PR's own PR-check run exercises that fixedbuild.yml; the publish path will use stable buildkit on the next push tomain.