fix: prune dangling images immediately on each deploy#21
Merged
SPerekrestova merged 1 commit intomainfrom Mar 24, 2026
Merged
Conversation
Replace 168h-filtered prune commands with immediate cleanup. Add post-build prune to clear the image replaced by each new build. Prevents disk exhaustion from accumulating 8.5 GB dangling images. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.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
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
docker image prunewith immediatedocker image prune -f(dangling only, safe for named images)until=168htountil=24hto prevent multi-GB stale cache accumulationdocker image prune -fto immediately reclaim the image replaced by each new buildRoot Cause
Each deploy produces a new ~8.5 GB image and leaves the old one as
<none>. With the 7-day filter, two stale builds (17 GB) accumulated alongside the current image, exhausting disk and causingno space left on devicemid-build.Test Plan
docker image prune -fto clear the currently accumulated dangling images (~17 GB)no space left on devicedocker system dfpost-deploy to confirm only the current image and nginx remain🤖 Generated with Claude Code