docker
config/pruning: add documentation on `docker builder prune`
Proposed changes
This adds a section documenting the docker builder prune command in the pruning documentation.
Related issues (optional)
Related: #15205 Fixes: #12236
Deploy Preview for docsdocker ready!
Built without sensitive environment variables
| Name | Link |
|---|---|
| Latest commit | 637a93ca46b02204311ea329e4afbcf9d0b6acdb |
| Latest deploy log | https://app.netlify.com/sites/docsdocker/deploys/6300063d7a531800099a3386 |
| Deploy Preview | https://deploy-preview-15437--docsdocker.netlify.app |
| Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site settings.
![netlify[bot] avatar](https://avatars.githubusercontent.com/in/13473?v=4 "Published by a pub.dev verified publisher"){kind=small}
I'm kinda not certain about that, because on one hand, you are correct in that it is out of scope for running applications in production. However, I have come across this page several times when trying to clean up space using Docker, by using a search engine and looking up something like "docker clean up space", "docker remove images", and even "docker prune" (it's the second article for this one! just after docker system prune, which I skipped, as I confused it with docker swarm / docker machine). The headline is appealing to people using search engines who just want an answer, so I believe this is the best place to put it, even if it may not be entirely relevant to people reading the manual in a linear fashion.
Maybe a similar section can be added to the builder section, but I think the SEO for this page is too valuable to not have such a critical piece of information missing, even if it's not entirely relevant to the chapter as a whole.
Thanks for the pull request. We'd like to make our product docs better, but haven’t been able to review all the suggestions. As our docs have also diverged, we do not have the bandwidth to review and rebase old pull requests.
If the updates are still relevant, review our contribution guidelines and rebase your pull request against the latest version of the docs, then mark it as fresh with a /remove-lifecycle stale comment.
If not, this pull request will be closed in 30 days. This helps our maintainers focus on the active pull requests.
Prevent pull requests from auto-closing with a /lifecycle frozen comment.
/lifecycle stale
