Self-host VictoriaLogs with Levelrail
A log database with a built in web UI and low memory use, with a data volume. Send logs to port 9428 from this project. The API has no login, so restrict access before exposing it.
- AuthorVictoriaMetrics
- LicenceApache-2.0
- Memory256 MiB
- Services1
How to self-host VictoriaLogs
-
Pull the images
One image is pulled on your server.
Show images
victoriametrics/victoria-logs:v1.53.0
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 9428.
-
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
- Ship logs to http://victorialogs:9428 from this project, then open the web UI to search them.
VictoriaLogs requirements
- Memory
- About 256 MiB
- Architectures
- amd64 unknown, arm64 unknown
- Ports
- 9428
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- Apache-2.0, 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 VictoriaLogs. 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 VictoriaLogs docs page.
Deploy VictoriaLogs your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy VictoriaLogs from the CLI
levelrail-cli templates deploy victorialogs --name my-victorialogs Deploy VictoriaLogs with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/victorialogs/deploy VictoriaLogs configuration
VictoriaLogs services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| victorialogs | victoriametrics/victoria-logs:v1.53.0 | 9428 | vlogs_data -> /victoria-logs-data |
VictoriaLogs environment variables
The catalog lists no environment variables for this template.
Ports and volumes
- Ports
- 9428
- Volumes
- 1 named mount: vlogs_data -> /victoria-logs-data
VictoriaLogs FAQ
How much memory does VictoriaLogs need?
The catalog lists about 256 MiB of memory for VictoriaLogs.
Does VictoriaLogs run on arm64?
For VictoriaLogs, arm64 support is not confirmed; amd64 is unknown.
What licence is VictoriaLogs under?
VictoriaLogs is licensed under Apache-2.0, which is permissive, with few conditions on reuse.
Does VictoriaLogs need configuration before it starts?
No. The template fills in its own defaults.
Which ports does VictoriaLogs use?
VictoriaLogs listens on port 9428 inside the stack.
Where does VictoriaLogs keep its data?
In a named volume: vlogs_data mounted at /victoria-logs-data.
Can I deploy VictoriaLogs 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 VictoriaLogs, 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 victoriametrics/victoria-logs:v1.53.0 is what you deploy there.