Self-host Kavita with Levelrail
VerifiedA fast, feature-rich reader server for manga, comics, and ebooks.
- AuthorKareadita
- LicenceGPL-3.0
- Memory256 MiB
- Archarm64
- Services1
How to self-host Kavita
-
Pull the images
One image is pulled on your server.
Show images
jvmilazz0/kavita:0.9.1
-
Create the app
One service starts in a single Compose app, with 2 named volume mounts for your data, on port 5000.
-
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.
Kavita requirements
- Memory
- About 256 MiB
- Architectures
- amd64 image published, arm64 tested
- Ports
- 5000
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- GPL-3.0, copyleft license
- Verified. Verified on arm64 with image tag 0.9.1. Our CI ran this exact image version and it answered on its health path. Evidence
- Host ports. It publishes port 5000 on the host, so open them in the VPS firewall only if you want that.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Kavita. 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 Kavita docs page.
Deploy Kavita your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Kavita from the CLI
levelrail-cli templates deploy kavita --name my-kavita Deploy Kavita with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/kavita/deploy Kavita configuration
Kavita services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| kavita | jvmilazz0/kavita:0.9.1 | 5000 | kavita_config -> /kavita/configkavita_data -> /manga |
Kavita environment variables
The catalog lists no environment variables for this template.
Ports and volumes
- Ports
- 5000
- Volumes
- 2 named mounts: kavita_config -> /kavita/config, kavita_data -> /manga
Kavita FAQ
How much memory does Kavita need?
The catalog lists about 256 MiB of memory for Kavita.
Does Kavita run on arm64?
For Kavita, arm64 is tested; amd64 is image published.
What licence is Kavita under?
Kavita is licensed under GPL-3.0, which is copyleft, so changes you distribute must be shared under the same terms.
Does Kavita need configuration before it starts?
No. The template fills in its own defaults.
Which ports does Kavita use?
Kavita listens on port 5000 inside the stack.
Where does Kavita keep its data?
In named volumes: kavita_config mounted at /kavita/config and kavita_data mounted at /manga.
Can I deploy Kavita 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 kavita for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image jvmilazz0/kavita:0.9.1 is what you deploy there.