I've enabled the exclusive shares option to bypass FUSE on a few of my shares, and now I'm having issues with directory mounts in a few docker containers. This makes sense since the exclusive shares use symlinks (ex. /mnt/user/appdata -> /mnt/cache/appdata). What's the best way to handle this? I fixed a few containers by mapping the appdata directory in /mnt/cache instead of /mnt/user, but I think it would be better to still be able to use '/mnt/user' for all paths.

2 minutes ago, D3r3k23 said:

having issues

What sort of issues? My appdata is an exclusive share but I still use /mnt/user/appdata for my containers.

12 minutes ago, trurl said:

What sort of issues? My appdata is an exclusive share but I still use /mnt/user/appdata for my containers.

I don't understand exactly. But it looks like the appdata share is still working. For example in my code-server container, /config is mounted to /mnt/user/appdata/code-server/config. I had the array mounted as /array -> /mnt/user, then accessed files in shares through /array/<SHARE>.I don't understand symlinks and docker mounts very well, but maybe that means mounting the share directly (/mnt/user/appdata) works when it's a symlink, but my previous method of only mounting /mnt/user doesn't?

Edited February 20Feb 20 by D3r3k23

17 minutes ago, D3r3k23 said:

but my previous method of only mounting /mnt/user doesn't?

This.

Never recommended to pass the entirety of /mnt/user to any container anyway as it gives it the ability to wipe your entire server, only pass what you need, do multiple mounts if needed...

Edited February 20Feb 20 by Kilrah

10 minutes ago, Kilrah said:

This.

Never recommended to pass the entirety of /mnt/user to any container anyway as it gives it the ability to wipe your entire server, only pass what you need, do multiple mounts if needed...

Great, that's easy to fix then. Thanks!