@OliverV
After testing different versions by building from Github I observed a general change in initializing the docker image/container. It seems since 1.32.0 when building the docker image it is pre-initializing nextcloud layer including all installed apps. This is cool because everything is in the image and starting of a container is much faster …
BUT because the user defined volume with “-v ncdata:/data” was not available during build time of the image, it will use data-ro folder when starting the container with the user defined volume. And in this case all user added data will be stored in data-ro instead of data.
With 1.31.0 the initialization of nextcloud was done on the first docker run of the container (including “-v ncdata:/data” option) when nextcloud sees an uninitialized created & mounted volume.
So I see the problem in this commit: https://github.com/nextcloud/nextcloudpi/commit/92156694f683d490a6bc2426e20dd356789d913b
I pulled 1.34.1 reverted the changes in
- docker/nextcloud/Dockerfile
- docker /nextcloud/020nextcloud
- docker/nextcloudpi/Dockerfile
to 1.31.0 and now /data will be created on first run on the docker container. And if the docker run mounts a volume to /data, all is good and user added data will be stored in the mounted volume.
I will create a bug ticket on github later.