Docker Hosts

Install the Vigilhold agent on a Docker host with one docker run command.

Quick start

In Vigilhold, click Add host, generate a command and choose the Docker tab. Run it on the Docker host:

docker run --rm --privileged --pid=host debian:stable-slim \
  nsenter -t 1 -m -u -i -n -- \
  sh -c "curl -fsSL https://__DASHBOARD_HOST__/install-agent.sh | bash -s -- --token '<token>' --dashboard 'wss://__DASHBOARD_HOST__/agent-ws'"

The container exits when the install finishes, in under a minute. The server appears in Vigilhold as soon as the agent connects.

How it works

The agent has to run on the host, not inside a container: from inside one it would only see that container's own processes. The command starts a throwaway container that enters the host (--pid=host lets nsenter reach the host's first process) and runs the normal Linux installer there. The agent ends up as the sentinel-agent service on the host (systemd, or OpenRC on Alpine), exactly as with the curl install.

Requirements:

Docker Desktop on macOS or Windows is not supported: its "host" is Docker's own virtual machine, and the installer stops before using your token.

Container inventory

When the agent finds the Docker socket on the host, it keeps a list of the containers running there. Each container appears in the server's Containers tab with:

Containers that exit are marked as exited.

Vigilhold's root helper reads the list from Docker every 30 seconds, read-only, so the agent needs no Docker access of its own (Docker access would be equivalent to root).

Security: container escape detection

The agent watches for a process breaking out of a container onto the host, or a process other than Docker's own opening the Docker socket, and raises an alert straight away with the process, its user and its command line.

Tips

All Vigilhold docs · Start a 14-day free trial