Self-host WebDAV Server with Levelrail
Small standalone WebDAV server with per user permissions. The install form carries config.yml as an editable file and a generated admin password.
- Authorhacdias
- LicenceMIT
- Memory32 MiB
- Services1
How to self-host WebDAV Server
-
Pull the images
One image is pulled on your server.
Show images
hacdias/webdav:v5.17.3
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 6060.
-
Fill in the secrets
You do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
After the first start
- Connect a WebDAV client to the address with the user admin and the generated password shown in the deployment variables.
WebDAV Server requirements
- Memory
- About 32 MiB
- Architectures
- amd64 unknown, arm64 unknown
- Ports
- 6060
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- MIT, permissive license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then WebDAV Server. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the WebDAV Server docs page.
Deploy WebDAV Server your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy WebDAV Server from the CLI
levelrail-cli templates install webdav --name my-webdav Deploy WebDAV Server with the API
curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
https://levelrail.example.com/api/v1/service-templates/webdav/install \
-d '{
"name": "my-webdav"
}' WebDAV Server configuration
WebDAV Server services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| webdav | hacdias/webdav:v5.17.3 | 6060 | data -> /data |
WebDAV Server environment variables
The catalog lists no environment variables for this template.
Ports and volumes
- Ports
- 6060
- Volumes
- 1 named mount: data -> /data
WebDAV Server FAQ
How much memory does WebDAV Server need?
The catalog lists about 32 MiB of memory for WebDAV Server.
Does WebDAV Server run on arm64?
For WebDAV Server, arm64 support is not confirmed; amd64 is unknown.
What licence is WebDAV Server under?
WebDAV Server is licensed under MIT, which is permissive, with few conditions on reuse.
Does WebDAV Server need configuration before it starts?
No. The template fills in its own defaults.
Which ports does WebDAV Server use?
WebDAV Server listens on port 6060 inside the stack.
Where does WebDAV Server keep its data?
In a named volume: data mounted at /data.
Can I deploy WebDAV Server on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for WebDAV Server, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image hacdias/webdav:v5.17.3 is what you deploy there.