Self-host Zipkin with Levelrail
A distributed tracing system that collects timing data from your services and shows request traces. This uses in-memory storage, so traces reset when the container restarts.
- Authoropenzipkin
- LicenceApache-2.0
- Memory512 MiB
- Services1
How to self-host Zipkin
-
Pull the images
One image is pulled on your server.
Show images
openzipkin/zipkin:3.6.1
-
Create the app
One service starts in a single Compose app, on port 9411.
-
Fill in the secrets
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.
After the first start
- Send spans to /api/v2/spans from your tracing library, then open the page to search traces.
Zipkin requirements
- Memory
- About 512 MiB
- Architectures
- amd64 unknown, arm64 unknown
- Ports
- 9411
- 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 Zipkin. 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 Zipkin docs page.
Deploy Zipkin your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Zipkin from the CLI
levelrail-cli templates deploy zipkin --name my-zipkin Deploy Zipkin with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/zipkin/deploy Zipkin configuration
Zipkin services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| zipkin | openzipkin/zipkin:3.6.1 | 9411 | none |
Zipkin environment variables
| Variable | Service | Value |
|---|---|---|
| JAVA_OPTS | zipkin | Preset by the template |
Ports and volumes
- Ports
- 9411
- Volumes
- none
Zipkin FAQ
How much memory does Zipkin need?
The catalog lists about 512 MiB of memory for Zipkin.
Does Zipkin run on arm64?
For Zipkin, arm64 support is not confirmed; amd64 is unknown.
What licence is Zipkin under?
Zipkin is licensed under Apache-2.0, which is permissive, with few conditions on reuse.
Does Zipkin need configuration before it starts?
No. The template fills in its own defaults.
Which ports does Zipkin use?
Zipkin listens on port 9411 inside the stack.
Can I deploy Zipkin 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 Zipkin, 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 openzipkin/zipkin:3.6.1 is what you deploy there.