Self-host Kopia with Levelrail
VerifiedFast, incremental, encrypted backups to a repository, driven from a web UI instead of a cron script.
- Authorkopia
- LicenceApache-2.0
- Memory512 MiB
- Archarm64
- Services1
How to self-host Kopia
-
Pull the images
One image is pulled on your server.
Show images
kopia/kopia:0.19.0
-
Create the app
One service starts in a single Compose app, with 4 named volume mounts for your data, on port 51515.
-
Fill in the secrets
2 secrets are generated and stored encrypted, 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.
Kopia requirements
- Memory
- About 512 MiB
- Architectures
- amd64 image published, arm64 tested
- Ports
- 51515
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- Apache-2.0, permissive license
- Verified. Verified on arm64 with image tag 0.19.0. Our CI ran this exact image version and it answered on its health path. Evidence
- Host ports. It publishes port 51515 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 Kopia. 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 Kopia docs page.
Deploy Kopia your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Kopia from the CLI
levelrail-cli templates deploy kopia --name my-kopia Deploy Kopia with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/kopia/deploy Kopia configuration
Kopia services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| kopia | kopia/kopia:0.19.0 | 51515 | kopia_repository -> /app/repositorykopia_config -> /app/configkopia_cache -> /app/cachekopia_logs -> /app/logs |
Kopia environment variables
| Variable | Service | Value |
|---|---|---|
| KOPIA_PASSWORD | kopia | Generated at deploy |
| KOPIA_SERVER_PASSWORD | kopia | Generated at deploy |
| KOPIA_SERVER_USERNAME | kopia | Preset by the template |
Ports and volumes
- Ports
- 51515
- Volumes
- 4 named mounts: kopia_repository -> /app/repository, kopia_config -> /app/config, kopia_cache -> /app/cache, kopia_logs -> /app/logs
Kopia FAQ
How much memory does Kopia need?
The catalog lists about 512 MiB of memory for Kopia.
Does Kopia run on arm64?
For Kopia, arm64 is tested; amd64 is image published.
What licence is Kopia under?
Kopia is licensed under Apache-2.0, which is permissive, with few conditions on reuse.
Does Kopia need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which ports does Kopia use?
Kopia listens on port 51515 inside the stack.
Where does Kopia keep its data?
In named volumes: kopia_repository mounted at /app/repository, kopia_config mounted at /app/config, kopia_cache mounted at /app/cache and kopia_logs mounted at /app/logs.
Can I deploy Kopia 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 Kopia, 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 kopia/kopia:0.19.0 is what you deploy there.