idelsink / webdav-docker Goto Github PK

I'm running idelsink/webdav from a docker-compose configuration on Docker for Windows (18.03.0-ce, build 0520e24).

docker-compose.yml:

version: '3'

services:
  webdav:
    image: idelsink/webdav
    environment:
      - USERNAME=webdav
      - PASSWORD=vadbew
    ports:
      - '8081:80'
    volumes:
      - '.webdav:/webdav'

I'm using WinSCP (5.13.1, build 8265) to interact with the container. Using WinSCP, I can connect to http://localhost:8081 using webdav/vadbew, and can navigate the files and download them. However, when trying to upload a file to the directory, WinSCP fails, reporting 500 internal server error

I attached to the container and viewed the apache logs, and I see these lines:

[Mon Apr 09 20:10:19.385323 2018] [dav:error] [pid 18] [client 172.18.0.1:33560] The locks could not be queried for verification against a possible "If:" header.  [500, #0]
[Mon Apr 09 20:10:19.385349 2018] [dav:error] [pid 18] [client 172.18.0.1:33560] Could not open the lock database.  [500, #400]
[Mon Apr 09 20:10:19.385355 2018] [dav:error] [pid 18] (2)No such file or directory: [client 172.18.0.1:33560] Could not open property database.  [500, #1]

Hi,

I'm having issues to make it work. My ip address is 3.17.182.115 and I used
docker run --name=iwebdav -d -v ~/webdav:/webdav -p 8082:80 idelsink/webdav to start it.
I can see that the folder ~/webdav is bided to the webdav folder in the container. So, isnt it right to use
3.17.182.115:8082/webdav to access it via browser?

Best regards,

Eduardo

I need for Tagspaces add /media folder in write acces, I can not rename

I've taken the adaption of the dockerfile setting the permissions have the following mounts in my compose:

 - /hdd/webdav:/webdav
      - /hdd/magazines:/webdav/magazines
      - /media/Documents/:/webdav/documents

So /hdd/webdav is a local folder to the machine.
The other two are samba mounts.

My user has read/write to all these folders. And if I upload/delete to the /webdav folder it is fine. But the mounted folders have a persmissions error (I can see 403 in the logs).

Is the container using a www-data user? If I didn't have one of those on the host, should i make one, so I can set access?