Closed masterlog80 closed 8 months ago
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
A human has marked this issue as invalid, this likely happened because the issue template was not used in the creation of the issue.
We do not offer support for making remote mounts work. I would suggest testing with local storage to rule out a container problem. If local (linux filesystem) storage works, this is not a container problem. Open a new ghi with the full template filled out in the case you still have issues with local storage.
Is there an existing issue for this?
Current Behavior
Hello, I am running docker-pyload-ng as 1000:1000 and it works fine, unless I need to store files to a SMB Share mounted locally. The Share is defined in the docker-compose file with correct login details for R/W, but Pyload is unable to store files there ("download failed" abd "permission denied" are shown in the logs). The only workaround I have found is run the Container as 0:0 (root), but other containers running as 1000:1000 can definirely write to that SMB Share. Any ideas to prevent this and run the container as 1000:1000?
Regards,
Expected Behavior
Being able to write to a SMB Share once running the Container as 1000:1000.
Steps To Reproduce
Environment
CPU architecture
x86-64
Docker creation
Container logs