Self-host Pyroscope with Levelrail
A continuous profiling database with a web UI and a data volume. The UI has no login, so restrict access before exposing it. Applications push profiles to port 4040.
- Authorgrafana
- LicenceAGPL-3.0
- Memory256 MiB
- Services1
How to self-host Pyroscope
-
Pull the images
One image is pulled on your server.
Show images
grafana/pyroscope:1.10.0
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 4040.
-
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
- Point profiling agents in this project at http://pyroscope:4040, then open the UI to explore flame graphs.
Pyroscope requirements
- Memory
- About 256 MiB
- Architectures
- amd64 unknown, arm64 unknown
- Ports
- 4040
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- AGPL-3.0, network copyleft (agpl) 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 Pyroscope. 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 Pyroscope docs page.
Deploy Pyroscope your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Pyroscope from the CLI
levelrail-cli templates deploy pyroscope --name my-pyroscope Deploy Pyroscope with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/pyroscope/deploy Pyroscope configuration
Pyroscope services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| pyroscope | grafana/pyroscope:1.10.0 | 4040 | pyroscope_data -> /data |
Pyroscope environment variables
The catalog lists no environment variables for this template.
Ports and volumes
- Ports
- 4040
- Volumes
- 1 named mount: pyroscope_data -> /data
Pyroscope FAQ
How much memory does Pyroscope need?
The catalog lists about 256 MiB of memory for Pyroscope.
Does Pyroscope run on arm64?
For Pyroscope, arm64 support is not confirmed; amd64 is unknown.
What licence is Pyroscope under?
Pyroscope is licensed under AGPL-3.0, which is network copyleft, so source sharing also applies when it is offered as a hosted service.
Does Pyroscope need configuration before it starts?
No. The template fills in its own defaults.
Which ports does Pyroscope use?
Pyroscope listens on port 4040 inside the stack.
Where does Pyroscope keep its data?
In a named volume: pyroscope_data mounted at /data.
Can I deploy Pyroscope 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 Pyroscope, 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 grafana/pyroscope:1.10.0 is what you deploy there.