Optimize Docker cleanup to preserve caching #6631
Draft
Conversation
This file contains 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
- Add disk space monitoring before build, after build, and after hash verification - Add Docker cleanup steps to free up space after major operations - Monitor largest files and directories to identify space usage - Use docker system prune and builder prune to clean up unused resources
- Replace aggressive docker system prune with targeted cleanup - Only remove dangling images and unused containers/volumes - Keep build cache for frequently used base images - Add time filter to only remove old containers (>1h) This should maintain better build performance while still managing disk space.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR optimizes the Docker cleanup strategy to better preserve caching while still managing disk space effectively.
Changes:
docker system prunewith targeted cleanup:This should help maintain better build performance (previous approach was taking ~12 minutes vs the usual 3-6 minutes) while still preventing disk space issues like the one seen in #6346.
To run this PR locally, use the following command: