Docker is affecting folder permissions, how do i reset after a specific time

Every time I turn my server on my folder permissions are fine. This is until my dockers start running 30s~ after startup , and they prevent me from writing to my folders over SMB unless I reset them within the GUI.

I've tried using the command /usr/sbin/omv-resetperms and creating a scheduled job upon reboot but this doesn't work for me, as the command is ran before the dockers startup.

Is there anyway to offset the command by a minute after startup or an alternative command that would achieve the same goal ?

Zitat von gderf

What are the permissions when you first turn on the server? What files and folders are invloved?

What do they become when things stop working?

Are you sure about what process is changing them? What process is that?

I would not rely on the OMV GUI to set permissions and unless you really understand what ACLs are, don't use them.

Alles anzeigen

The folder in question is my ZFS pool, this is where all of my data, outside of the OMV system, is stored.

On startup the folder privileges have my user account set to Read/Write. Under ACLs the owner is root with Read/Write/Execute set as permissions, users and other also have Read/Write/Execute. None of these settings are changed after the permissions break, or after I use the GUI reset permissions tool, however that does enable me to write to the folders.

The error I get over SMB is "You require permission from Unix User\admin to make changes to this folder."

Zitat von flhtk

There is a plugin for OMV called reset perms or something like that. Look for a youtube video by Jeff from TDL TechnoDadLife. The install is quick and it resolves the changed permissions for shared folders caused by Docker and/or Portainer.

If you're like me you'll end up using it almost every time you add, update or change a Docker container.

I have it and I have to use it every time my server turns on. That's what I'm trying to avoid.

Zitat von KM0201

Well have you actually set permissions for the share?... When you set up the SMB share, did you make sure you enabled 'Honor Existing ACL's'?

SMB perms are set to non-public, non-read only, browsable share with honour ACLs active.