Self-host Baikal with Levelrail
A lightweight CalDAV and CardDAV server for calendars and contacts.
- Authorsabre-io
- LicenceGPL-3.0
- Memory128 MiB
- Services1
How to self-host Baikal
-
Pull the images
One image is pulled on your server.
Show images
ckulka/baikal:0.10.1-nginx-php8.2
-
Create the app
One service starts in a single Compose app, with 2 named volume mounts for your data, on port 80.
-
Fill in the secrets
1 setting is preset, 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.
Baikal requirements
- Memory
- About 128 MiB
- Architectures
- amd64 unknown, arm64 unknown
- Ports
- 80
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- GPL-3.0, copyleft 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 Baikal. 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 Baikal docs page.
Deploy Baikal your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Baikal from the CLI
levelrail-cli templates deploy baikal --name my-baikal Deploy Baikal with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/baikal/deploy Baikal configuration
Baikal services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| baikal | ckulka/baikal:0.10.1-nginx-php8.2 | 80 | baikal_config -> /var/www/baikal/configbaikal_data -> /var/www/baikal/Specific |
Baikal environment variables
| Variable | Service | Value |
|---|---|---|
| TZ | baikal | Preset by the template |
Ports and volumes
- Ports
- 80
- Volumes
- 2 named mounts: baikal_config -> /var/www/baikal/config, baikal_data -> /var/www/baikal/Specific
Baikal FAQ
How much memory does Baikal need?
The catalog lists about 128 MiB of memory for Baikal.
Does Baikal run on arm64?
For Baikal, arm64 support is not confirmed; amd64 is unknown.
What licence is Baikal under?
Baikal is licensed under GPL-3.0, which is copyleft, so changes you distribute must be shared under the same terms.
Does Baikal need configuration before it starts?
No. The template fills in its own defaults.
Which ports does Baikal use?
Baikal listens on port 80 inside the stack.
Where does Baikal keep its data?
In named volumes: baikal_config mounted at /var/www/baikal/config and baikal_data mounted at /var/www/baikal/Specific.
Can I deploy Baikal on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list has an entry with the id baikal for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image ckulka/baikal:0.10.1-nginx-php8.2 is what you deploy there.