Dashboard for the chrony daemon
281
The application can be configured using environment variables.
| Variable | Default | Description |
|---|---|---|
TZ | Etc/UTC | Timezone used by the application. |
CHRONY_USE_SUDO | true | Whether to execute chronyc through sudo. Set to false when the container user can access the Chrony command socket directly. |
CHRONY_SOCKET | unset | Path to the Chrony Unix command socket. When set, chronyc is invoked with -n -h <socket>. |
For example:
TZ: "Europe/Warsaw"
CHRONY_USE_SUDO: "false"
CHRONY_SOCKET: "/var/run/chrony/chronyd.sock"
With this configuration, the application executes:
chronyc -n -h /var/run/chrony/chronyd.sock clients
The application can be run as a container using the provided Dockerfile:
docker build -t ticc-dash .
docker run --rm -p 5000:5000 ticc-dash
When running alongside a Chrony container, mount the Chrony runtime socket into the dashboard container:
docker run --rm -v /var/run/chrony:/var/run/chrony:ro -p 5000:5000 ticc-dash
The container by default listens on port 5000.
| Problem | Solution |
|---|---|
| ❌ No clients showing | Run sudo chronyc clients manually to verify |
| ⚙️ Service not starting | Check logs: sudo journalctl -u ticc-dash.service -f |
| 🔒 Port already in use | Free port 5000 or put a reverse proxy (e.g., Nginx) in front |
| 🧩 Missing logo | Ensure ticc-dash-logo.png exists under /opt/ticc-dash/static/img/ |
More tips: https://ticc-dash.org/docs.html#troubleshooting.
Released under the MIT License.
© 2025 – TICC‑DASH Project.
Content type
Image
Digest
sha256:c4d570114…
Size
21.3 MB
Last updated
3 months ago
docker pull venthe/ticc-dash