PHP-FPM UID + GID incompatible with Nginx UID + GID
almereyda opened this issue · 3 comments
When using the Nextcloud image with the supplied Compose example there will be errors with retrieving files from the file system.
The error will be similar to:
stat() "/var/www/html/custom_apps/mail/img/mail.svg" failed (13: Permission denied)
as described in Proper permissions after upgrade/migration? - ℹ️ Support / 📦 Appliances (Docker, Snappy, VM, NCP, AIO) - Nextcloud community
It is useful to chown -R 33:101 the volume mapped into both containers for mitigation.
References:
docker/28/fpm-alpine/entrypoint.sh
Lines 99 to 100 in 473af1b
This extends:
Which other strategies have people found to resolve this, eventually without chown'ing the state?
Maybe it is easier nowadays to run from Caddy #2052?
Or it is better to build an Nginx container that runs from www-data/33 as well?
Surprised this hasn't come up earlier.
Can you post your compose file and OS variant/version? I have updated two production instances to 29 today, both are effectively a copy-paste from the fpm-nginx example (with some stuff added) and i have no such issues, they both have a bunch of apps including mail but no permission errors.
Are you, perhaps, using bind mounts rather than actual volumes? (This would be different than the examples).
It'd probably be best if you shared your actual Compose file. :-)
Also, keep in mind that technically nginx is only serving files. It only needs read permission. FPM does all the heavy lifting, including anything that requires write permissions.
I'm going to close this since there wasn't a response to the query for additional info >30 days ago. I suggest following up at the community help forum: https://help.nextcloud.com