Repository navigation
Cache never cleaned #261
Description
Entries in the cache managed by Chisel (storing, among other things, files from the archive) never expire. On a developer machine, this cache can grow over 10Go over time. This can also become problematic in the context of a CI building environment sharing the cache to build multiple images.
Currently the cache can be manually and safely cleaned between chisel executions. But doing so while retaining the advantages of the cache might be uneasy and be burden.
Automatically cleaning old entries in the cache could be a nice UX improvement.
Reacted by Alberto Carretero, Brennan Kinney, Gajesh Bhat and Marcin Konowalczyk
Activity
fix: add support for sha512-only archives (#306)
lczyk commentedon Oct 23, 2026
a data point from a dev machine (mine, this one) that has run chisel daily for a few months:
~/.cache/chiselis 38G in 14935 blobs, 9490 of them untouched for a week or more.Cache.Expireis already there ininternal/cache/cache.go(!) all it would take is to call it after a cut with something likeExpire(7 * 24 * time.Hour).a side-effect of this bug(?)/shortcoming is that anything that takes views into the cache (e.g. someone's so-far-private work-in-progress chisel tools) keep seeing larger and larger cache and keep getting more and more sluggish. i'm half tempted to start expiring chisel's cache for it from other tools, but i shan't. separation of concerns and all..
lczyk commentedon Oct 23, 2026
given the above i'm gonna tentatively label this as Bug. ff to unlabel ofc.
<digest>.tmp#340<digest>.tmp#340<digest>.tmp#340lczyk commentedon Oct 23, 2026
4 thumbs up + it's a tentative blocker for any work looking like #340 + this is really simple to fix. adding appropriate labels.