Update docs gc policy docs to mention that the policies are documented in the buildx prune command #21584
Conversation
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
github-actions
bot
added
the
area/build
✅ Deploy Preview for docsdocker ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
It took me a long time to realize these policies were documented in the buildx prune command itself.
dvdksn
approved these changes
Dec 9, 2024
Contributor
dvdksn
left a comment
dvdksn
left a comment
There was a problem hiding this comment.
Good start
I need to add more details/examples, but happy to merge this to begin with
Contributor
Author
|
It's also confusing that although docker buildx inspect shows ==, and the toml format expects ==, the json format only wants a single '='... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
I spent a lot of time searching for the documentation of the specific policies (like
all) and finally realized these are just arguments passed to buildx prune.