I get a bit confused about some advice in some forum posts about specifying the docker appdata setting to a path under /cache. As I understand it, if you simply have the appdata share configured to cache only, this is enough to ensure the container settings are stored in cache - i.e. what you specify in container appdata is where the appdata share will be mounted (in addition to showing up under /mnt/cache/appdata)?! In my case I have appdata configuration in docker set to /mnt/user/appdata/.

 

Similarly if I have specified that the system share should be stored on cache only, is it enough to specify docker file location as /mnt/user/system/docker/docker.img to have it residing in cache (i.e. is the system share mounted as /mnt/user/system?)? Also for this I have seen some mention of specifying a location under /mnt/cache but this seem pointless to me?!

 

I have tried finding the recommended settings for Docker vdisk and appdata (as mentioned above my understanding is /mnt/user/system/docker/docker.img and /mnt/user/appdata/) but has failed...

 

Can somebody confirm or correct my understanding of this?

If the pool is set to cache only using /mnt/user is the same, through for some containers, performance may be better it /mnt/cache, unless you set the shares to exclusive, then it would be the same.

3 hours ago, JorgeB said:

If the pool is set to cache only using /mnt/user is the same, through for some containers, performance may be better it /mnt/cache, unless you set the shares to exclusive, then it would be the same.

I have only shares for appdata, domains, isos and system only on cache and syslog and some other folders for media etc as cache->array.  Nothing explicitly for /mnt/user (this is not even a share by default in UNRAID). I was kind of assuming the share "system" was mounted as /mnt/user/system - is this not the case?

/mnt/user works with all shares, if a share exists, it can be accessed under /mnt/disk#_or_pool_name/share_name and /mnt/user/share_name