@tal@lemmy.today That post is somehow deleted by the mod so I could only reply here

I’m not personally familiar with Synology’s products, but if what’s going on is that you’re using some built-in feature of a Synology NAS to copy files from a USB drive to the NAS and seeing an error, I’d probably try copying that particular file to somewhere else on a PC, cutting the NAS out of the loop, to make sure that you don’t have, say, a corrupt filesystem where attempts to read the file contents are failing.

USB Copy is a built in application in synology. I set it up to do mirroring backup of several folders each day. Copy files to a PC works for me but not a long term solution

Thanks!

The question is asked, yet no actual answer is given for the article.
A usual secure way is to set the bind-mounted modes to u+rwx and ownership to the container User UID, which you may check via docker inspect <container> or its image.

Meanwhile, nice choice for the NodeRed! ✨

User namespaces are an advanced feature and require coordination with other capabilities. For example, if volumes are mounted from the host, file ownership must be pre-arranged if you need read or write access to the volume contents.
Source: https://docs.docker.com/engine/security/userns-remap

thank you!

Mario hosting runs a bunch of guides for docker containers on synology. Maybe follow his guide and see if it fixes your issue.

The issue is I have VPN enabled. Very unexpected

The issue is I have VPN enabled. Very unexpected

I think its you device‘s path, i.e. on Android - otherwise the error would look different I presume.

Yes, /emulated/0/my-smb-mount or similar looks about right.

Is this Path option referring to the path on my android mobile? I thought it is referring to the path of my synology NAS.

Should I use exact path of android or relative path? I'm not quite sure what is the full path of my android mobile. But I think it is something like ...emulated/0/...

I have added Path in material files setting using FOLDERNAME and /FOLDERNAME but neither worked. What exact syntax should I use to fill in Path option?

EDIT: just want to provide more info: I have 7 Shared folders under Volume 1 in my synology NAS. docker, home, homes... and I can access those shared folders in windows explorer by tying //NasName

Are you potentially trying to mount a SMB share to the root folder on your client (i.e. / )? The error looks like the client is attempting to do something it itself is not allowed on its machine. Try specifing a path to mount to which is writable - e.g. /tmp/mount (not that you should keep mounting there if it works).

Yep, this is how SMB works when using Linux - I can't explain why, but that's always been my experience when either side is Linux - you just get a cryptic error.

I was just fighting this earlier today trying to connect to my networked photo frame (which runs Linux). I'd forgotten the share name, and Windows Explorer couldn't open just the server name. Once I added the share name it opened no problem.

You may need to include a path. You might need to add each of your Shared folders separately. I have had this issue with Samba before where the host was browseable, but you could not mount the whole server.