Having the davlock file under the mapped volume can be problematic.

Question

Having the davlock file under the mapped volume can be problematic.

mlabbe opened this issue 5 years ago · 1 comments

Apache requires that the davlock file is writable by the user and group of the httpd process. In my case, the volume maps to a samba share which gave it a different UID. This caused a cryptic error on startup.

My workaround was to map the /var/lib/dav/data directory instead, which is not what the docs specified. It might be useful to have the docs explain this subtlety.

Answer 1 · 2019-08-17T01:26:11.000Z

This ended up being part of a larger problem with permissions on my end. Once my volume was mapped to uid/gid 82 (to match www-data) everything started working.