You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docker-entrypoint.sh currently makes it very hard to run a Nextcloud container in an isolated dynamic user namespace. Because UIDs are not known on the host before starting a container in such an environment, setting the correct file permissions to allow fine grained write access for the user running fpm or apache is impossible.
Looking at someotherentrypoints usually this problem is mitigated by a simple chown -R.
The text was updated successfully, but these errors were encountered:
docker-entrypoint.sh currently makes it very hard to run a Nextcloud container in an isolated dynamic user namespace. Because UIDs are not known on the host before starting a container in such an environment, setting the correct file permissions to allow fine grained write access for the user running fpm or apache is impossible.
Looking at some other entrypoints usually this problem is mitigated by a simple
chown -R
.The text was updated successfully, but these errors were encountered: