Permissions of mounted /data folder get set to PUID and PGID and all other permissions removed

[rottenkumquat]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Permissions for the share mounted as /data are set to the permissions of the configured PUID and PGID. All other users and groups get removed.

Expected Behavior

Leave permissions alone?

Steps To Reproduce

..

Environment

- OS: Synology DMS 7.2
- How docker service was installed: Container Manager

CPU architecture

x86-64

Docker creation

Container Manager

Container logs

..

[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]

Permissions of that mount need to be set to the same uid/gid that nextcloud is running as so it can manage those files. Nextcloud is designed to work like this and ideally you shouldn't just be directly accessing that folder.

[rottenkumquat]

That is fine and all. But what justification is there for removing other permissions I set there?

[j0nnymoe]

The files need to be owned by the user of the container. Realistically you shouldn't be changing anything inside that folder anyways. If you -must-, just make your user have the same group as you're running for the container.

[rottenkumquat]

Funny you should say that, because ownership is not changed.

[thespad]

You're running on Synology which means it applies its own ACLs over the filesystem, which are impossible for us to see or modify from inside the container. Setting the raw Linux permissions will reset the ACLs and there's not a clean solution to that. However, we only chown the root of /data so any folders under that can have ACLs set without being affected.

[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.

[github-actions]

This issue is locked due to inactivity