ci(manual-build): bring disk-cleanup fixes onto staging#719
Merged
Conversation
The release/80009 → staging PR (#714) merged before the CI-side disk-cleanup fixes were ready. Subsequent commits to release/80009 fixing the 'No space left on device' on the self-hosted runner are orphaned (the PR is already closed). This PR brings the final state of those fixes directly to staging. Reclaim step now: * prints docker system df + buildx_buildkit_* volume list before and after, so future failures show exactly where disk is going * drops stopped containers + dangling images * removes orphaned buildx_buildkit_* state volumes from prior builder instances * iterates every still-existing buildx builder and caps each one's cache at 30 GiB Observed empirically on dev: reclaimed 36 GiB on a runner sitting at 86% used (mostly from leaked stopped containers carrying overlay writable layers).
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.
Summary
blockchain-node#714 (release/80009 → staging) merged at the first version of the
manual-buildworkflow's disk-cleanup step, which turned out to be a no-op. The fixes that actually reclaim disk landed onrelease/80009later as five iterative commits — those are now orphaned because the PR was already closed.This PR brings the final version of
.github/workflows/manual-build.yamldirectly to staging, squashed into one commit.What the Reclaim step now does
docker system dfand the list ofbuildx_buildkit_*volumes before AND after — diagnostic visibility for future failuresdocker container prune --force— drops stopped containers (this turned out to be the real disk hog: 36 GiB freed on a runner at 86% usage)docker image prune --force— drops dangling untagged imagesEach command is
|| trueso the step never blocks the build on an edge case.Observed result
On a fresh build from
release/80009: 124 GiB → 88 GiB used (reclaimed 36 GiB), build then completed successfully.Test plan
docker system dfand the post-prunedf -h /shows reclaimed disk