Is your cron container running the same image as your nextcloud container? It sounds like maybe one is the -alpine image and other not maybe? (You want them to be the same image).
The alpine images use 82/www-data. The debian images use 33/www-data.
Oh no…I do have both container using fpm-apline image, but I didn’t know fpm-alpine is for alpine linux. Does that mean raspbian cannot use it?
Or is it because I had nextcloud docker setup before and the user id for www-data was 33, now if i switched to fpm-alpine it won’t work out very well? (I’m using fstab to automount my ntfs with owner www-data, which is currently 33)
(Right now I have everything in fpm-apline, which makes me wonder how the world it works in my raspbian…)
Or is it because I had nextcloud docker setup before and the user id for www-data was 33, now if i switched to fpm-alpine it won’t work out very well? (I’m using fstab to automount my ntfs with owner www-data, which is currently 33)
Do you know if there a way I can make www-data in the fpm-apline version of nextcloud container to use id 33 instead of 82?
I saw there was a git issue but it seems to be shut down quickly by the “user” option in docker compose file. After trying that “user: 33:33” in my docker compose file for all nextcloud related containers, I found this option didn’t work out well for me. I started seeing some permission error in my nextcloud docker, not too sure what’s going on there.
Another method I tried was using the command: docker exec nextcloud chown -R www-data:root /var/www (nextcloud is my nextcloud container name), but that didn’t work out either.
Right now I guess I’ll have to change my www-data on host to 82 instead of 33, and then automount my ntfs drive to 82