docs: add docker builder prune to pruning page#24429
Open
dvdksn wants to merge 1 commit intodocker:mainfrom
Open
docs: add docker builder prune to pruning page#24429dvdksn wants to merge 1 commit intodocker:mainfrom
dvdksn wants to merge 1 commit intodocker:mainfrom
Conversation
Fixes docker#17590. Adds a new "Prune build cache" section covering docker builder prune, including the --all flag for removing all build cache (not just dangling entries). Co-Authored-By: Claude Sonnet 4.6 <[email protected]>
✅ Deploy Preview for docsdocker ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
![docker-agent[bot]](https://avatars.githubusercontent.com/in/2787757?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Assessment: 🟢 APPROVE
This PR adds comprehensive documentation for docker builder prune to the pruning page. The new section follows the established pattern of other prune sections and is well-structured.
Review Summary:
- ✅ No vendored content edited
- ✅ No missing redirects (no pages removed/moved)
- ✅ Markdown formatting is correct
- ✅ No AI-isms or style guide violations in new content
- ✅ Scope preservation maintained (matches existing sections)
- ✅ Content accuracy verified (commands are correct)
- ✅ CLI reference link is valid
- ✅ Consistent with existing documentation patterns
The new "Prune build cache" section clearly explains:
- What build cache is and why it grows
- How to remove dangling build cache
- How to remove all build cache with
--all - Links to the CLI reference for more details
No issues found in the changed code.
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
Fixes #17590.
The pruning documentation page was missing coverage of
docker builder prune. This PR adds a new Prune build cache section before the existing "Prune everything" section, following the same style as the other sections on the page.Changes:
docker builder pruneremoves dangling build cachedocker builder prunecommand with its confirmation prompt--allflag for removing all build cache, not just dangling entriesdocker builder pruneCLI referenceTest plan
/reference/cli/docker/builder/prune/resolves correctly🤖 Generated with Claude Code