Self-host Vector with Levelrail
High performance observability data pipeline for logs and metrics. The install form carries vector.yaml as an editable file, so it starts with an HTTP source and a console sink.
- Authorvectordotdev
- LicenceMPL-2.0
- Memory128 MiB
- Services1
How to self-host Vector
-
Pull the images
One image is pulled on your server.
Show images
timberio/vector:0.61.0-alpine
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on ports 8686, 8080.
-
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
- Post JSON to port 8080 and watch the container log, then edit the config file setting to add transforms and real sinks. The API is on port 8686.
Vector requirements
- Memory
- About 128 MiB
- Architectures
- amd64 unknown, arm64 unknown
- Ports
- 8686, 8080
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- MPL-2.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 Vector. 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 Vector docs page.
Deploy Vector your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Vector from the CLI
levelrail-cli templates install vector --name my-vector Deploy Vector with the API
curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
https://levelrail.example.com/api/v1/service-templates/vector/install \
-d '{
"name": "my-vector"
}' Vector configuration
Vector services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| vector | timberio/vector:0.61.0-alpine | 8686, 8080 | data -> /var/lib/vector |
Vector environment variables
The catalog lists no environment variables for this template.
Ports and volumes
- Ports
- 8686, 8080
- Volumes
- 1 named mount: data -> /var/lib/vector
Vector FAQ
How much memory does Vector need?
The catalog lists about 128 MiB of memory for Vector.
Does Vector run on arm64?
For Vector, arm64 support is not confirmed; amd64 is unknown.
What licence is Vector under?
Vector is licensed under MPL-2.0, which is copyleft, so changes you distribute must be shared under the same terms.
Does Vector need configuration before it starts?
No. The template fills in its own defaults.
Which ports does Vector use?
Vector listens on ports 8686 and 8080 inside the stack.
Where does Vector keep its data?
In a named volume: data mounted at /var/lib/vector.
Can I deploy Vector 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 Vector, 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 timberio/vector:0.61.0-alpine is what you deploy there.