Self-host Radicale with Levelrail
VerifiedCalendar (CalDAV) and contacts (CardDAV) server. One user is created at first boot with a generated password (visible in the service environment settings, never on a process command line); it is stored as a SHA-512 hash in /var/lib/radicale/users and each user only sees their own collections. Add users by appending htpasswd lines to that file.
- AuthorKozea
- LicenceGPL-3.0-or-later
- Memory128 MiB
- Archarm64
- Services1
How to self-host Radicale
-
Pull the images
One image is pulled on your server.
Show images
kozea/radicale:3.9.0
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 5232.
-
Fill in the secrets
2 secrets are generated and stored encrypted, 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.
Radicale requirements
- Memory
- About 128 MiB
- Architectures
- amd64 image published, arm64 tested
- Ports
- 5232
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- GPL-3.0-or-later, copyleft license
- Verified. Verified on arm64 with image tag 3.9.0. Our CI ran this exact image version and it answered on its health path. Evidence
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Radicale. 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 Radicale docs page.
Deploy Radicale your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Radicale from the CLI
levelrail-cli templates deploy radicale --name my-radicale Deploy Radicale with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/radicale/deploy Radicale configuration
Radicale services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| radicale | kozea/radicale:3.9.0 | 5232 | data -> /var/lib/radicale |
Radicale environment variables
| Variable | Service | Value |
|---|---|---|
| RADICALE_PASSWORD | radicale | Generated at deploy |
| RADICALE_USER | radicale | Generated at deploy |
Ports and volumes
- Ports
- 5232
- Volumes
- 1 named mount: data -> /var/lib/radicale
Radicale FAQ
How much memory does Radicale need?
The catalog lists about 128 MiB of memory for Radicale.
Does Radicale run on arm64?
For Radicale, arm64 is tested; amd64 is image published.
What licence is Radicale under?
Radicale is licensed under GPL-3.0-or-later, which is copyleft, so changes you distribute must be shared under the same terms.
Does Radicale need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which ports does Radicale use?
Radicale listens on port 5232 inside the stack.
Where does Radicale keep its data?
In a named volume: data mounted at /var/lib/radicale.
Can I deploy Radicale 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 Radicale, 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 kozea/radicale:3.9.0 is what you deploy there.