Saved Template Cleanup

Saved Template Cleanup

Saved Docker templates can remain after containers are removed. This manager handles those saved configuration files separately from appdata cleanup.

Open Saved template cleanup from the action bar, then review templates and backups. It is separate from Tools. The compact dialog gives long template lists their own scrollable area.

Archive

The plugin identifies templates whose containers are not installed. Before archiving, it rechecks ownership and the current template revision, creates and verifies a private backup, and only then removes the original saved template.

Archiving does not delete appdata, Docker images or containers. A missing container also does not prove you will never want its saved configuration again.

Restore

Choose the backup's restore action. Restore requires the original template filename to be free; it does not overwrite a replacement template. The backup is retained after restore.

Restoring a template does not recreate or start a container. Use Unraid's Docker workflow to install/configure the application afterwards.

Backup location and privacy

Backups are stored under:

/boot/config/plugins/appdata.cleanup.plus/template-backups/

Templates can contain paths, names and environment secrets. Treat their backups as private configuration. Do not attach them to a public issue. Sanitized diagnostics do not export their raw contents.

Template backups are not automatically purged. Uninstalling the plugin removes its configuration directory, including these backups. Preserve any needed copies independently before uninstalling.

A blocked archive or restore should be investigated using the reported ownership, revision or filename-conflict reason rather than by manually overwriting files.