You can always loosen permissions, later, with the Users group and with "Others" permissions.ĭo the same as the above but map directly to the root of your data drive. This will mean that you'd need to delete the existing share and the "Downloads" folder (Copy any existing data to another location.) This process allows the appropriate account to create the Downloads folder and assign permissions that the container can use. This time around, let the container create the folder "Downloads". There are two scenarios that I would try: This points back to the container and/or the installation parameters. With others having Read/Write, even the root account inside the container (different from OMV's root account, BTW) should be able to write to it. Import failed, path does not exist or is not accessible by Sonarr: /srv/9a94fceb-ff72-4c70-9562-591fcc600b9e/Fileserver/Downloads/.Tomorrow.x264-BAMBOOZLE Images My Apologies I did not see the question about WinSCP.
Since I don't use this particular Docker, I don't know how the container interacts with the host. The above is an attempt to resolve the "denied" error dialog you provided. It's far easier to look at standard, unshared folders and change their permissions, with WinSCP, versus doing the same on the command line. This is why I asked if you have WinSCP installed. Change Fileserver to "Others", "Read / Write". If a shared folder is not at the root of the drive, the entire path to the shared folder needs to have compatible permissions.
I've experienced the same sort of problem with permissions when I shared a sub-directory, under a root folder, of the data drive. (Note that the reset perm's plugin won't help you with this.) Apply the same permissions that were applied to "Downloads", to "Fileserver". OK, you have a folder called "Fileserver" in the path.
0 kommentar(er)
