fix: limit dagger-data volume growth by pruning named caches (#193) #197

Merged
guettlibot merged 1 commits from issue-193-fix into main 2026-05-24 04:00:18 +00:00
1 Commits
Author SHA1 Message Date
Thomas SharedInboxandClaude Sonnet 4.6 bd94d0babe fix: limit dagger-data volume growth by pruning named caches (#193)
The plain `prune` operation only removes unreferenced execution-cache
entries; named cache volumes (gradle-cache, go-build-cache, go-mod-cache,
pip-cache) are never reclaimed and grow without bound, causing the
dagger-data Docker volume to reach 200 GB over time.

Pass maxUsedSpace/targetSpace arguments to `prune` so Dagger also
reclaims named volumes when the total cache exceeds 75 GB, targeting
50 GB. Use an aggressive targetSpace of 20 GB for disk-space emergency
recovery in check-dagger. Add a dagger-prune task for manual use.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-05-24 05:51:40 +02:00