Docker Containers

Any agent already installed on a host is enough — if that host runs a Docker daemon, Guardian discovers its containers automatically. There’s nothing to configure, no separate collector to install, and no credentials to enter.

How it works

The agent checks for a local Docker daemon every 2 minutes and, if one is running, reports the full current container list to the hub — name, image, state, status, and published ports. Each report replaces the previous one for that host, so the list always reflects what’s running right now, not a stale history.

Viewing containers

Containers in the sidebar lists every discovered container across your fleet: which host it’s running on, its image, current state (running, exited, paused, restarting), Docker’s own status string (e.g. “Up 3 hours”), and any published ports. Use the filter box to narrow by container name, image, or host.

Platform support

Linux and macOS hosts are fully supported today. Windows hosts running Docker Desktop aren’t yet — Docker Desktop exposes its API over a named pipe rather than the Unix socket this feature currently talks to, a real gap planned as a follow-on rather than built half-right.

For VMs rather than containers, see Hypervisors. Kubernetes cluster discovery (nodes and pods, not just standalone containers) is scoped but not yet built — see the project roadmap.