i created my own image from Dockerfile from this repo: juanitomint/nextcloud-client
Let me explain what i am doing:
i need to sync encfs encrypted volume to nextcloud.
i use encfs in the --reverse mode, where the ‘sync’ folder is the encrypted output of my files.
When i start the nextcloud-client, it tries to create the /media/pi/data/sync path, which it should not in the first place, since the docker-compose.yml tells to mount the /media/pi/data/sync folder as ‘/media/nextcloud’ within the docker container, and not create the source dir.
Did you check the behavior on one of the common filesystems like ext4 or xfs?
I wouldn’t be surprised if capabilites of encfs are responsible for the behavior. There must be a reason why docker thinks the folder is not existing. Since the docker engine is always run as root, it should not suffer from a lack permissons (though, the process in the container will).
Ofcourse docker works just fine. But the error docker reports isnt sane either.
By saying that its trying to create a dir of a pre-existing source volume, is not a correct error being reported to the user.
Is there any way to debug it whats actually happening while trying to mount an encfs volume?