Glances
Inspect resource metrics through a web interface and REST API.
Choose your deployment and the way you want to use Selfhost. The instructions below follow that choice.
Set up Glances
Editable Compose files in your own directory.
- The default web deployment listens on port 61208 and runs without a Docker socket or host privileges.
- Use the native command option field for supported Glances web settings and mount extra configuration only when needed.
selfhost app --directory ./glances init glances Initialization writes portable files and does not start the app. Review compose.yaml, the private .env and any files in files/, then start it:
selfhost app --directory ./glances startNo Selfhost dashboard or background service is needed. You can also start these files directly:
cd glances
docker compose -f compose.yaml up -dBefore configuring integrations
- This isolated container reports the resources visible inside its namespace.
- Full host monitoring, container discovery and hardware metrics require explicit host resources and permissions.
- Host PID namespace, devices and Docker socket access are not silently enabled.
- Secure access through an authenticated reverse proxy; this recipe does not provision identity provider integration.
Glances integrations
Compose service: glances. These operations use the profile saved when this deployment is created.
Native settings
Changes use the app’s Compose environment. Unrelated settings are preserved.
Supported fields (2)
- GLANCES_OPT
glances-opt - string · advanced
- TZ
tz - string · advanced
Save a JSON map of the field IDs you want to change as changes.json. Replace FIELD_ID with an ID from the supported fields above, and use its declared value type. Review the plan and replace REVIEWED_REVISION with the revision it returns.
{
"FIELD_ID": "YOUR_VALUE"
}selfhost app --directory ./glances config glances
selfhost app --directory ./glances plan glances changes.json
selfhost app --directory ./glances apply glances changes.json --revision REVIEWED_REVISION Saved changes need service recreation to become active. Existing interpolated environment values stay under your control in .env or Compose.
App actions
Show version
Show Glances and dependency versions.
selfhost app --directory ./glances action glances check-versionVersions and updates
This deployment uses the following images. Existing projects retain their saved recipe and images. A new catalogue version does not silently update them.
- glances:
nicolargo/glances:4.5.6-full
- 4.5.6-full
nicolargo/glances:4.5.6-fullLocal Docker HTTP startup, native configuration roundtrip, declared read-only actions and container recreation with persistent volumes passed. External provider login and version upgrades require separate validation.
Review compatibility and back up app data before an update. Choose an image version and review the change.
Keep control of your setup
Selfhost remains optional. Your app runs using ordinary Compose files, its own settings and persistent data. Keep the Compose project name and volumes to preserve storage. Configuration exports and setting backups do not include application data.
Standalone CLI guide · Backups and removal · Glances documentation