- Annoyance
Hi,
Not sure if this is unraid or community apps, but since it's now so closely integrated with a single button install, I'm going to post this here. Please move if needed.
On a new server, I created an "appdatapool" pool:
Next, I made the appdata share an exclusive share with just that pool:
My docker is configured to use /mnt/user/appdata as default appdata storage:
Some containers, like IBRACORP's jellyseerr, seem to use the /mnt/user/appdata share correctly:
However, it seems they just have it hardcoded in their template:
Other containers, like linuxserver's sonarr, will follow the symlink (according to the docs, exclusive shares are symlinks I believe?)
Checking out their template, the Appdata path has no default, and should be filled from my docker config, I believe?
Now, if I make the share not an exclusive share:
And I try to install linuxserver's sonarr again, it does take my configured appdata share:
The docs (https://docs.unraid.net/unraid-os/manual/docker-management/#appdata) suggest that the appdata share should be used ("By convention the appdata share is used for this purpose, with each container using a container specific sub-folder in this location."). When I have an exclusive share, already bypassing the FUSE system and overhead, my appdata defaults to the pool, it seems to resolve the symlink. When not having an exclusive share, and one might actually want to put the appdata directly on the pool and not the share to bypass FUSE, the share is being used correctly.
I know, it's just a few click to change this, but it's easy to forget an can cause issues down the line (for example, creating a new pool for appdata while keeping the old one in place, restoring a backup and changing the appdata share to use that, suddenly your appdata will be randomly split between 2 pools).