Better documentation for auto-prune semantics #895
Replies: 2 comments 1 reply
-
Pruning might be a bit aggressive in case your image disk's size is 30+% of the host disk. Auto-pruning is a bit aggressive:
Meaning that if you have 200GB image on a host with 512GB SSD. Then if you'll clone this image twice than auto-pruning will clean up OCI cache. If you are certain in what you do, you can try to disable pruning via |
Beta Was this translation helpful? Give feedback.
-
i can't even find the official documentation link page lol |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
In the help text of
tart clone
, you will find this:This is confusing in several ways:
TART_NO_AUTO_PRUNE
- but again, there has been no mention of pruning at all at this point.What I have noticed, though, is that once I run out of space, all my cached OCIs and IPSWs are lost. In my case, all my VMs are ephemeral, so it is much more annoying to prune OCIs (which I will have to re-download) than it is to prune VMs. I understand why OCIs are purged first - that seems like a safer default.
For me, ideally, I would like to disable auto-pruning while preserving the free-space safety check.
Beta Was this translation helpful? Give feedback.
All reactions