Self-host Traccar with Levelrail
An open-source GPS tracking platform supporting over 170 device protocols.
- Authortraccar
- LicenceApache-2.0
- Memory1 GiB
- Archarm64
- Services2
How to self-host Traccar
-
Pull the images
2 images are pulled on your server.
Show images
traccar/traccar:6.6postgres:16-alpine
-
Create the app
2 services start in a single Compose app, with 1 named volume mount for your data, on port 8082.
-
Fill in the secrets
2 secrets are generated and stored encrypted, 6 settings are 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.
Traccar requirements
- Memory
- About 1 GiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 8082
- 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.
- Host ports. It publishes port 8082 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 Traccar. 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 Traccar docs page.
Deploy Traccar your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Traccar from the CLI
levelrail-cli templates deploy traccar --name my-traccar Deploy Traccar with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/traccar/deploy Traccar configuration
Traccar services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| traccar | traccar/traccar:6.6 | 8082 | none |
| traccar-db | postgres:16-alpine | none | traccar_postgres_data -> /var/lib/postgresql/data |
Traccar environment variables
| Variable | Service | Value |
|---|---|---|
| CONFIG_USE_ENVIRONMENT_VARIABLES | traccar | Preset by the template |
| DATABASE_DRIVER | traccar | Preset by the template |
| DATABASE_PASSWORD | traccar | Generated at deploy |
| DATABASE_URL | traccar | Preset by the template |
| DATABASE_USER | traccar | Preset by the template |
| POSTGRES_DB | traccar-db | Preset by the template |
| POSTGRES_PASSWORD | traccar-db | Generated at deploy |
| POSTGRES_USER | traccar-db | Preset by the template |
Ports and volumes
- Ports
- 8082
- Volumes
- 1 named mount: traccar_postgres_data -> /var/lib/postgresql/data
Traccar FAQ
How much memory does Traccar need?
The catalog lists about 1 GiB of memory for Traccar across its 2 services.
Does Traccar run on arm64?
For Traccar, an arm64 image is published; amd64 is image published.
What licence is Traccar under?
Traccar is licensed under Apache-2.0, which is permissive, with few conditions on reuse.
Does Traccar need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which database does Traccar bundle?
The template includes Postgres, running as its own service.
Which ports does Traccar use?
Traccar listens on port 8082 inside the stack.
Where does Traccar keep its data?
In a named volume: traccar_postgres_data mounted at /var/lib/postgresql/data.
Can I deploy Traccar 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 Traccar, 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 traccar/traccar:6.6, postgres:16-alpine is what you deploy there.