Regarding the SMB-share, let my try to clarify.
Let's say you have 3 machines. 192.168.1.10/20/30. On machine 10 a folder synology which has a network folder mounted onto it from machine 20 mount -t nfs 192.168.1.20:/some/folder synology.
Now you want to access that folder on machine 30. Here you can't use mount -t nfs but MUST use mount -t cifs instead, because you cannot forward a mounted share. However, this is not the problem, it's just a description of my current setup.
Regarding the ownership. Your point is very valid, but I ruled that out already. I did a so-called bind-mount within Synology with the exact user permissions as in the users home folder, but this didn't work.
FYI: a bind-mount is where you have two folders /foo (with many sub-folders and files) and /bar (empty). If you do mount --bind /foo /bar, then the system thinks that bar is a real folder with the subfolders and files (from foo, including their permissions).
and yet, it somehow made it into a kids game. The core issue here is the uncontrolled content display.
Imagine some NSFW ads slip through into a kids app. Therefore, ads must be forbidden in apps intended for underaged.
I'd highly recommend to take a deeper look into Docker. While it might look complicated at first, it really isn't. Once you get the gist of it, you'r setup life will me much simpler in the future.
In a nutshell: Say you need to run jellyfin (or whatever)
Generally, you'd need to install jellyfin from the repos or download it's binary, etc... Then you'd have to dig through the configuration process, where files are scattered all across the system. Probably, in some cases, you'd have to copy/move/symlink media files around, etc.
With Docker however, you just spin up the jellyfin as a container, and bind the necessery configuration and media files to that container, which is usually a one-liner.
So instead of having scattered config files all around the place, you can have something like ~/Docker/configs/jellyfinn and bind that folder (or file) to the containers /etc/jellyfin. And you can use the same approach to have your media files in ~/Movies and bind thst to jellyfin /data folder. These are just examples, you'll just have to look where the docker containers expect the files to be, which is usually well documented.
And the final step is to bind the ports of the container to the host, so you can interact with the service as if it was running on the host.
Obviously, with the fact that the Palestinians have been opressed for decades, which led for organisations like the Hamas to arrise, there's no good guys / bad guys in this situation.
Now imagine being a freelance developer, who works for more than two clients, using Teams with different email addresses.
It's a horror!