What DockLog does
Tail logs, check host stats, manage containers. No Elasticsearch cluster required.
Live log streams
stdout/stderr over WebSockets. No polling delay.
Container-level RBAC
Wildcard or regex visibility rules plus two-layer action rights: server ALLOW_* gates and per-user can_* flags.
CPU and memory
Host and container stats with live updates. About 30 days of history in SQLite.
Small footprint
Go 1.26 backend, ~30MB RAM typical. One container image.
Optional database
No-auth without DB_PATH runs in-memory. Mount a volume when you want users and audits to survive restarts.
Container controls
Start, stop, restart, remove, and optional shell when both server and user permissions allow. Container actions are audit-logged in auth mode.
Where people use it
A few patterns we see a lot. Nothing industry-specific, just practical.
Prod and staging on one host
Give each developer a container pattern so they tail their own services without seeing prod databases or unrelated stacks.
Small team, shared VPS
Auth mode, RBAC rules, audit log. Everyone gets log access without handing out SSH keys to the whole box.
Homelab or NAS
One image, socket mount, done. Works on Pi and small cloud instances where you do not want another service to babysit.
Client or agency work
Hand a client read-only log access to their stack without opening the full Docker daemon or your internal containers.
Try it on your server
Setup guide has compose examples, env vars, and proxy notes.