Self-host SmokePing with Levelrail
A latency and packet loss monitor that pings your targets and graphs jitter over time. GPL-2.0 licensed. Targets live in the Targets file under the config volume. There is no login, so keep it private or behind an auth proxy.
- Memory192 MiB
- Archarm64
- Services1
How to self-host SmokePing
-
Pull the images
One image is pulled on your server.
Show images
lscr.io/linuxserver/smokeping:2.9.0
-
Create the app
One service starts in a single Compose app, with 2 named volume mounts for your data, on port 80.
-
Fill in the secrets
3 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.
SmokePing requirements
- Memory
- About 192 MiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 80
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- not yet recorded
- 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 SmokePing. 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 SmokePing docs page.
Deploy SmokePing your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy SmokePing from the CLI
levelrail-cli templates install smokeping --name my-smokeping Deploy SmokePing with the API
curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
https://levelrail.example.com/api/v1/service-templates/smokeping/install \
-d '{
"name": "my-smokeping"
}' SmokePing configuration
SmokePing services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| smokeping | lscr.io/linuxserver/smokeping:2.9.0 | 80 | config -> /configdata -> /data |
SmokePing environment variables
| Variable | Service | Value |
|---|---|---|
| PGID | smokeping | Preset by the template |
| PUID | smokeping | Preset by the template |
| TZ | smokeping | Preset by the template |
Ports and volumes
- Ports
- 80
- Volumes
- 2 named mounts: config -> /config, data -> /data
SmokePing FAQ
How much memory does SmokePing need?
The catalog lists about 192 MiB of memory for SmokePing.
Does SmokePing run on arm64?
For SmokePing, an arm64 image is published; amd64 is image published.
Does SmokePing need configuration before it starts?
No. The template fills in its own defaults.
Which ports does SmokePing use?
SmokePing listens on port 80 inside the stack.
Where does SmokePing keep its data?
In named volumes: config mounted at /config and data mounted at /data.
Can I deploy SmokePing 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 SmokePing, 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 lscr.io/linuxserver/smokeping:2.9.0 is what you deploy there.