Server cleanup
BetaReclaiming disk on a server. One schedule for the instance, individual hosts opt out.
Reclaiming disk. This is the setting people wish they had found earlier.
Beta
This feature is currently beta/experimental and subject to change. It is not recommended for production. Try it out and share your feedback on our GitHub.
How it works
Settings -> Servers -> the server -> Cleanup. One schedule for the whole instance, and individual hosts opt out of it, so a server you add tomorrow can never silently go unswept.
What gets cleaned
Prop
Type
Settings
Prop
Type
What it deliberately never does: system prune, container prune, volume
prune, network prune. On a Deplo host a stopped app is a live app, and
a dangling volume may hold somebody's data.
Limits and gotchas
- Cleanup and rollbacks fight over the same images. If rollbacks stop working, Images kept per app is too low for the app's Keep.
- This is not what frees the disk after you delete something. Cleanup reclaims images, caches and the directories of apps that are gone. It never touches a volume, and it never touches a server folder an app reached through a Bind - those are yours to remove.
- Backup files are not on this list either. Deleting a backup schedule leaves the copies it already made in the destination.
If it does not work
- Cleanup frees nothing: the minimum age is protecting everything, or the only large thing on disk is images your apps still use.
See Servers and agents for more.
See also
Did this page help you?