GHCR provides
latest and versioned images for linux/amd64 and linux/arm64. Versioned
tags omit the v prefix.
Images are also mirrored to Docker Hub.
docker run --rm \
-p 127.0.0.1:9090:9090 \
ghcr.io/pvrlabs/statlite:latestOpen http://127.0.0.1:9090. The image includes a default configuration that
monitors StatLite itself through statlite-metrics; no configuration file is
required.
Note
The bundled configuration polls every 30 seconds; allow a few polls for charts to populate.
The container stores SQLite data at /data/statlite.sqlite. Data is ephemeral
unless /data is mounted to persistent storage. See
Monitor an application.
The demo above polls StatLite itself. To poll your application, mount a
config over /etc/statlite/statlite.yaml and mount /data when you want to
keep history.
Inside the container, 127.0.0.1 is StatLite. The published dashboard is
reachable when that config listens on 0.0.0.0:9090. Keep the published port
on host loopback, as in the command below.
Point the target at host.docker.internal and the application port. Bind the
application on an address that interface can reach. A process listening only
on the host loopback is not reachable at that name. Docker Desktop resolves
host.docker.internal. On Linux, --add-host below provides the name.
server:
listen: "0.0.0.0:9090"
storage:
sqlite_path: "/data/statlite.sqlite"
polling:
interval: "30s"
targets:
- name: "app"
type: "spring"
url: "http://host.docker.internal:8080/actuator"For Express, Django, FastAPI, Go net/http, and Gin, use
type: statlite-metrics and the /statlite/metrics URL from the
integration guides. A file written on the host by
statlite inspect --create-config uses 127.0.0.1:9090 and
./statlite.sqlite. Before mounting that file, set server.listen to
0.0.0.0:9090 and storage.sqlite_path to /data/statlite.sqlite, and point
the target URL at host.docker.internal.
docker run --rm \
-p 127.0.0.1:9090:9090 \
--add-host=host.docker.internal:host-gateway \
-v "$PWD/statlite.yaml:/etc/statlite/statlite.yaml:ro" \
-v statlite-data:/data \
ghcr.io/pvrlabs/statlite:latestYou can also add the self-monitoring target to this targets list. Its URL
remains http://127.0.0.1:9090/statlite/metrics because that address is
inside the container.
The examples publish port 9090 only on host loopback. Publishing with
-p 9090:9090 instead binds all host interfaces by default and can expose
StatLite directly to the network. For remote access and proxy networking, see
Security and Remote Access.
Container resource metrics describe the environment visible inside the container, not the physical macOS host.
The image runs as the non-root statlite user and includes CA certificates for
HTTPS targets. Dashboard assets and the SQLite schema are embedded in the
binary.
From the repository root:
docker build \
--build-arg VERSION=dev \
-t statlite:local \
.Check the embedded version:
docker run --rm statlite:local --versionFor local development, the bundled image configuration listens on
0.0.0.0:9090 inside the container and the example above restricts access at
the host port.
Application examples are available under examples/, including the Spring
Boot and Python FastAPI demos.
Maintainers may publish a temporary :dev image for pre-release verification.
Build and inspect it from the repository root:
docker buildx build \
--platform linux/amd64,linux/arm64 \
--build-arg VERSION=dev \
--tag ghcr.io/pvrlabs/statlite:dev \
--push \
.
docker buildx imagetools inspect ghcr.io/pvrlabs/statlite:devSee the published container images
and release notes for versioned
and :latest images.