Unraid automatically fills docker paths to the name of the 'cache' drive rather than 'user'

[dopeytree]

Some kind of built in script to either suggest the path or some way of auto filling.

 

Basically unraid already knows where you appdata share is as your have to tell unraid which drive to put the share on...

 

So can we use that input to output the drive path to places that ask for 'appdata'.

 

so detect the word 'appdata' and offer to fill with the direct path for use in docker containers etc.

Edited September 22, 2023 by dopeytree

[itimpi]

2 minutes ago, dopeytree said:

Some kind of built in script to either suggest the path or some way of auto filling.

 

Basically unraid already knows where you appdata share is as your have to tell unraid which drive to put the share on...

 

So can we use that input to output the drive path to places that ask for 'appdata'.

 

so detect the word 'appdata' and offer to fill with the direct path for use in docker containers etc.

not sure what you are really asking for here?

 

If you are 6.12.x or later releases with exclusive mode enabled for the appdata share then accessing /mnt/user/appdata is as efficient as accessing the drive directly

[MAM59]

Hmm, I think, this is already builtin?

If I add a new docker it instantly offers /mnt/<mydockerpool>/appdata/<new path> folder instead of /mnt/user...

 

[itimpi]

18 minutes ago, MAM59 said:

Hmm, I think, this is already builtin?

If I add a new docker it instantly offers /mnt/<mydockerpool>/appdata/<new path> folder instead of /mnt/user...

 

If the share is set to be exclusive these are effectively the same thing anyway.

[dopeytree]

Ah ok. Maybe my docker is using my old templates which are /user/  I always have to manually change.

 

I read something in the powertop thread about SHFS being the 'fuse' process and you can save some cpu power by renaming to /cache's name/

[itimpi]

27 minutes ago, dopeytree said:

I read something in the powertop thread about SHFS being the 'fuse' process and you can save some cpu power by renaming to /cache's name/

That is no longer required in the 6.12.x releases as setting a share to Exclusive mode achieves the same performance benefits without needing the rename.