Please describe what you are doing to trigger the bug:
Using the duplicacy:testing docker image.
I have 2 backup jobs pointing to a mapping of a smb share. Those setup as backups to local directory works fine. Now to avoid having the smb share exposed on the host, i created a docker volume with the cifs driver. If i now add an existing repo from that volume i can run a check and it works. As soon as i try to init a new repo (or run a backup on it) it fails with permission denied.
If i bash into the container and do a manual init via cli it works fine and the repo gets created.
Please describe what you expect to happen (but doesn’t):
Behavior should be the same via web as via manual init via cli
Please describe what actually happens (the wrong behaviour):
Running /app/.duplicacy-web/bin/duplicacy_linux_x64_2.7.2 [-log -d init -e -storage-name SMB_Test duplicacyweb /backupdrive/test
ERROR CONFIG_INIT Failed to configure the storage: open /backupdrive/test/config.vrmpbmfq.tmp: permission denied
Failed to initialize the storage at /backupdrive/test: Failed to configure the storage: open /backupdrive/test/config.vrmpbmfq.tmp: permission denied