The logs on the container are just a loop of this:
+ '[' -f /dev-dri-group-was-added ']' + set +x Configuring Redis as session handler... Setting php max children... The www-data user doesn't seem to have access rights in the datadir. Most likely are the files located on a drive that does not follow linux permissions. Please adjust the permissions like mentioned below. The found permissions are: 33:0 750 (userID:groupID permissions) but they should be: 33:0 750 (userID:groupID permissions)
My system is fresh and up to date Ubuntu 22.04.
I use mergerfs to tie multiple hard drives into a single mount point.
I’m attempting the install with docker compose, using a datadir on the host. That datadir points to a mergerfs mounted directory with the correct permissions (33:0 750) which the nextcloud installation created.
The mergerfs people seem pretty certain that these kind of issues are no their cause because the permissions are handled by the kernel.
Another test with installing a standalone nextcloud docker, it worked if I pointed it to the underlying disk mount, but not when I pointed it at the mergerfs mount. Mounted directories inside the container showed d??? as the permissions for the bind mounted volumes.
Has anyone come across this or any idea what’s causing this?
Many people seem to be running this setup just fine, but somehow I just can’t. I’ve been trying for at least a week now.