# Container Health Check

> Full Docker infrastructure health assessment. Lists containers, images, volumes, and networks, then retrieves logs from a running container.

- Skill: `knuckles-team/container-health-check` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add knuckles-team/container-health-check`
- Raw SKILL.md: https://api.skillmd.com/api/skills/knuckles-team/container-health-check/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- Author: Knuckles-Team (https://skillmd.com/u/knuckles-team)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/knuckles-team/container-health-check

---


# Container Health Check Workflow

**CONCEPT:INFRA-001**

Full Docker infrastructure health assessment. Lists containers, images, volumes, and networks, then retrieves logs from a running container.

## Steps

### Step 0: list-containers [skill: container-manager-mcp]
**Agent**: `discovery-agent`
**Tools**: `tun_tm_system, tun_tm_hosts`

List all running containers and their current status
Expected: `container, running, status`

### Step 1: list-images [skill: container-manager-mcp]
**Agent**: `deployer-agent`
**Tools**: `pt_stack, cnt_cm_compose_operations`

List all Docker images with their sizes and tags
Expected: `image, tag`

### Step 2: list-storage-and-networks [skill: container-manager-mcp]
**Agent**: `verifier-agent`
**Tools**: `pt_docker, cnt_cm_container_operations`

Show all Docker volumes and networks
Expected: `volume, network`

### Step 3: fetch-container-logs [skill: container-manager-mcp]
**Agent**: `dns-configurator`
**Tools**: `adg_rewrites, td_zones`

Get the logs for one of the running containers
Expected: `log`

### Step 4: KG Persistence [depends_on: Step 0, Step 1, Step 2, Step 3]
**Agent**: `dns-configurator`
**Tools**: `graph_write`

Persist workflow results as nodes and edges in the Knowledge Graph.
Create appropriate typed nodes with metadata and link to existing domain entities.

## Output
- Container Health Check results persisted in KG
- Structured report (MD/PDF)
- Audit trail with timestamps and agent attributions

## Execution

Run this workflow as a dependency-ordered DAG. Steps with no unmet `depends_on` run in parallel; dependents run after their prerequisites complete.

- **Run first (in parallel):** Step 0 — list-containers; Step 1 — list-images; Step 2 — list-storage-and-networks; Step 3 — fetch-container-logs
- **After level 0:** Step 4 — KG Persistence

**Execution:** If graph-os is reachable, offload the whole DAG via `graph_orchestrate action=execute_workflow` (or the `kg-delegate` skill) for true parallel/swarm execution. Otherwise execute the steps natively in dependency order: run steps with no unmet `depends_on` in parallel, then their dependents.