Repository navigation
fix: bypass bootc-image-builder-action on ARM64 - #48
Merged
Merged
Conversation
The bootc-image-builder-action's internal githubActionsWorkaroundFixes() tries to rm -rf /var/lib/containers/storage but fails on ARM64 runners because the overlay mount is busy. This cascades into libpod_lock errors that prevent both podman pull and the BIB container from running. Run BIB directly via podman on ARM64 to skip the action's broken cleanup. On x86_64, continue using the action as-is. 🤖 Generated with Codebuff Co-Authored-By: Codebuff <noreply@codebuff.com>
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
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.
The `bootc-image-builder-action` has a known bug on ARM64 runners: its internal `githubActionsWorkaroundFixes()` runs `rm -rf /var/lib/containers/storage`, but the overlay mount is busy because the runner already has podman state. This cascades into `libpod_lock: numerical result out of range` errors that prevent both `podman pull` and the BIB container from running.
Fix: On ARM64, bypass the action entirely and run BIB directly via `podman run`:
On x86_64, continue using the action as-is (it works fine there).
This is an upstream issue in `osbuild/bootc-image-builder-action#446` — the action's internal cleanup conflicts with ARM64 runner podman state.
🤖 Generated with Codebuff
Co-Authored-By: Codebuff noreply@codebuff.com