container_diagnosis

To diagnose a restarting Docker container, the Skill checks container status via docker ps, reviews recent logs with docker logs, and inspects configuration using docker inspect to identify the root cause.

Checking Docker container CPU and memory usage is done by running docker stats to retrieve real-time resource utilization data, which is then compiled into a structured diagnostic report for stability analysis.

Finding out why a Docker container failed to start involves inspecting the container's status and configuration with docker inspect, and reviewing startup logs via docker logs to pinpoint initialization errors.

Diagnosing containers in a multi-host Docker Swarm environment is not supported, as this Skill applies specifically to single-host Docker environments for status checks, log review, and configuration inspection.

Container diagnosis generates a structured RCA report by executing a deterministic workflow of docker CLI commands including docker ps, docker stats, docker logs, and docker inspect, then aggregating the outputs into a final diagnostic conclusion.