Two kinds of host
Docker commands are addressed through DockerHostRef, which can refer to either:
- An SSH session jump host — containers are reached by running
docker execover the session's exec channel. - The local daemon — the CLI is spawned directly, which avoids quoting problems.
Local probing (probe_local_docker) tries docker first and then podman, and
distinguishes “not installed” from “installed but the daemon is not running”. That distinction matters when diagnosing
why a container list is empty.
Container operations
- List containers and create, delete, start and stop them.
- One-shot and streaming logs.
- A three-layer analysis report.
- Browse container files.
- Open a shell inside a container.
Host analysis
analyze_host performs a read-only inspection of the server: OS, kernel, architecture,
installed packages and installed tools. command_help looks up help for a command.
Read-only versus mutating actions
Analysis commands are read-only. Container start, stop, restart, delete and shell access are mutating operations that run immediately; deleting a Kubernetes resource asks for in-app confirmation first.
Related chapters
- Chapter 3 — Sessions & tabs: Docker logs are one of the pane content types.
- Chapter 8 — Kubernetes & Helm: the same “host follows the focused terminal” rule.