Repository navigation
fix: remove anonymous volumes on down and limit gc to them - #2
Merged
Merged
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
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.
devctl downleft every anonymous volume of the project behind (node_modules, MySQL and Manticore data), so a new one piled up on every down/up cycle. On one machine that was ~60 volumes, ~15 GB.downcollects the project's anonymous volumes (including stopped containers) beforedocker compose downand removes them only if the down succeeded. Named volumes are left alone.gcand thedoctorwarning now filter onlabel=com.docker.volume.anonymous. Before,dangling=truealone also listed named volumes with no container, i.e. real databases.Tests: 368 OK, ruff check and format clean.