how to not set file permsions when using new 10 docker setup

[jamie]

I’m doing the Espo 10 Docker upgrade, and our entire uploads folder is mounted from a Samba share. We therefore need Espo to accept the existing file ownership and permissions rather than trying to change them.

With Espo 10, every time the Docker container starts, it recursively tries to change the permissions on the mounted files. This doesn’t work correctly with the Samba share.

Is there a way to tell Espo to skip permission changes for this directory?

[jamie]

Is this really not a possibility? Why is permission handling enforced in the first place?

The upload folder contains all of the documents uploaded to Espo, so I would think it is a prime candidate for allowing administrators to choose where and how those files are stored. In our case, they are stored on a NAS and backed up off-site, which is very different from the Espo application code itself.

If anyone else runs into this problem, you’ll need to create your own entrypoint file and modify the setPermissions section so that it excludes the mounted upload directory.