[BUG] Folder permissions get reset when (re)starting syncthing docker container

[jensb]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

I am running the syncthing docker container on a Synology NAS. The folder where syncthing stores its data is also shared using SMB. I have set up the root folder permissions so that multiple users can access this folder.

But whenever I restart the syncthing docker container, these settings get reset so that only I (admin) can access this folder.

Is there anything in the docker container startup scripts that changes the permissions of the shared config folder?

Expected Behavior

No change of permissions in /config shared folder during startup.

Steps To Reproduce

1. Install the docker container on a Synology NAS
2. share the folder used for Syncthing data also via SMB using Synology with multiple users
3. Start up the container
4. Watch as the file permissions get reset so that only one (the admin user) can access this folder

Environment

- OS: Synology NAS
- How docker service was installed: using the Syncology Container Manager

CPU architecture

x86-64

Docker creation

Using the synology container manager

Container logs

There is no mention of permissions or security related in the logs.
However, there are a lot of personal data (folder names, share names, device names) in the logs so I hesitate to make them public. If these are really required, please provide a private email to send them to. Thanks!

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[j0nnymoe]

Need you to provide the actual details you've used to deploy the container otherwise it's going to be a struggle to help.

[LinuxServer-CI]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

[jensb]

Sorry, I must have missed your email. Which details specifically do you need?

[LinuxServer-CI]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.