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
{{ message }}
Repository navigation
build-pr CI check broken: qemu-user-static unavailable on Ubuntu 26.04 runners #3142
On PR #3140, the build-pr check failed in 14 seconds. The workflow at .github/workflows/build_pr.yaml runs sudo apt install -y buildah qemu-user-static, which errors: "Package 'qemu-user-static' has no installation candidate" on Ubuntu 26.04. This is systemic — the last 10 build-pr runs across all branches fail with the same error. Every PR shows a red image-build check that has nothing to do with code quality.
What could go better
Like the bandit failure, a perpetually failing build check creates CI noise that degrades developer and agent trust in CI signals. It is impossible for agents to use this check as a signal for image build correctness when it never passes. High confidence: the root cause is confirmed — the qemu-user-static package is not available in Ubuntu 26.04 default repositories.
Proposed change
Update .github/workflows/build_pr.yaml to fix the qemu-user-static installation. Recommended approach: pin the runner to ubuntu-24.04 where the package is available (runs-on: ubuntu-24.04). Alternative: install qemu-user-static from an alternative source compatible with Ubuntu 26.04, or use a container-based action that bundles the required qemu binaries.
Validation criteria
The build-pr check should pass (or fail only on actual build issues) on the next 3 PRs after the fix. Verify on both main and release/0.6 branches.
The fix for this issue requires modifying .github/workflows/build_pr.yaml, which the code agent cannot do under current permissions. A human must open the PR.
The recommended fix is to pin the runner:
runs-on: ubuntu-24.04
This restores access to qemu-user-static while a longer-term solution (e.g., sourcing qemu binaries independently of the runner OS) can be evaluated.
Related:#3141 tracks a similar Ubuntu 26.04 runner breakage for the bandit CI check — both issues stem from the ubuntu-latest alias advancing to 26.04.
Proposed test:
# After merging the fix, verify on a new PR:
# 1. build-pr check passes (apt install succeeds)
# 2. Multi-arch image build (amd64 + arm64) completes
# 3. Verify on both main and release/0.6 branches
Next steps:
/fs-code — agent creates a PR to implement this issue
/fs-code <your instruction> — agent implements with your specific guidance
Activity
fullsend-ai-triage commentedon Nov 3, 2026
🤖 Finished Triage · ✅ Success · Started 4:25 PM UTC · Completed 4:28 PM UTC
Commit:
06b5567· View workflow run →Runtime: pi · Model: opus → claude-opus-4-6 · Effort: high · Cost: $0.51
fullsend-ai-triage commentedon Nov 3, 2026
⚠ Workflow change required — manual intervention needed.
The fix for this issue requires modifying
.github/workflows/build_pr.yaml, which the code agent cannot do under current permissions. A human must open the PR.The recommended fix is to pin the runner:
This restores access to
qemu-user-staticwhile a longer-term solution (e.g., sourcing qemu binaries independently of the runner OS) can be evaluated.Related: #3141 tracks a similar Ubuntu 26.04 runner breakage for the bandit CI check — both issues stem from the
ubuntu-latestalias advancing to 26.04.Proposed test:
Next steps:
/fs-code— agent creates a PR to implement this issue/fs-code <your instruction>— agent implements with your specific guidance