Appdata Sources

Appdata Sources

A source is a directory whose appdata children should be considered during filesystem discovery. It is not a deletion target by itself.

Automatic and manual roots

Docker's configured appdata root is detected when available. Use Appdata Sources for additional/custom locations.

1. Open the source browser.
2. Browse to the directory that contains your application folders.
3. Add it to the manual source list.
4. Save the source configuration and rescan.
5. Check the resulting paths and detection reasons.

For appdata under /mnt/cache/custom-appdata/example-app, the intended source is normally /mnt/cache/custom-appdata, not the example application's directory or the entire pool.

Removing a manual source changes scan coverage. It does not delete folders. Broad roots can produce unexpected coverage and must pass source validation. Unavailable roots, symlinks and protected paths should be investigated rather than bypassed.

Nested and alternate paths

Unraid user shares and physical pool paths can refer to the same data. The plugin performs canonical/path-alias checks, but configuring an alternative spelling is not a way to evade ownership protection.

A nested source cannot relax a protective reference established within an outer configured source. Unknown source boundaries remain conservative.

ZFS mappings

The mapping editor associates a user-share root with a physical dataset root, for example:

Share root	Physical root
/mnt/user/appdata	/mnt/cache/appdata

Use your actual pool. Mappings help resolve ZFS storage, not discover extra rows or grant permission to destroy a dataset. Saving mappings can include the current valid draft. See ZFS Datasets.

Window layout

Dev 2026.09.19.14+: the source dialog is shorter, capped by the viewport and a 760px maximum, with its content scrolling inside and title/Done controls remaining available. This is a presentation change, not a change to source validation.