dlandon / unassigned.devices

Unassigned Devices plugin for unRAID
Other
81 stars 39 forks source link

Rare behaviour when browsing remote shares within docker container #91

Closed SmartPhoneLover closed 1 year ago

SmartPhoneLover commented 1 year ago

Hello, I would like to report a bug, that I'm not sure why it's happening, but I think it started to be noticable (for me) after updating to 2023.01.08b. I'm using unRAID 6.10.3.

Description of the problem... I can browse all the files and folders that are located on all the shares (remotes) mounted on the current server, coming from other servers in the same LAN. Also, doing 'cd (cmd)' via Terminal from host, and browsing the shares using other docker containers such as: Krusader/Fileborwser, I can reach the files/folders inside these remote shares. But, when I try to browse them within, in this case: Borgmatic container (/mnt/remotes is configured with an internal path within the container to allow backing up from them using borg), after doing cd (cmd) on its terminal, I can't see anything inside any of the remotes mounted.

Here are some pics as an example (sorry for the poor quality): Here you can see the shares are mounted on the host, usng UD plugin: 3483495893839_1

Here you can see that the mounted shares can be browsed without problems, using the built-in unRAID browser and/or other docker containers, such as: Krusader/Filebrowser, and also Terminal: 3483495893839_2 3483495893839_3

Here you can see that I can also see and browse all the dirs under every remote mount from the docker template of Borgmatic: 3483495893839_4

Here you can see that once I enter the Borgmatic terminal's it cannot see any directory inside any of the remote mounts: 3483495893839_5

It's only solved if I change something, or something from the SMB Settings from its settings sections in unRAID. But, after restarting the server, it starts over again.

Thank you.

dlandon commented 1 year ago

If Unraid and Docker Continers can see the files in the /mnt/remotes/ directory except for Borgmatic terminal, you need to look to Borgmatic for a solution. I suspect a permissions issue.