container-debug

To debug a crashing Docker container, you need to inspect its logs and exec into the environment to check runtime state. This Skill diagnoses container failures by analyzing logs, validating file systems, and identifying crash causes or OOM kill events.

Docker Compose connectivity failures often stem from network misconfigurations or DNS resolution issues. This Skill troubleshoots networking by verifying service discovery, checking port bindings, and confirming cross-container connectivity to isolate dependency breaks.

To find the cause of a Docker OOM kill, you must investigate resource usage and memory pressure within the container. This Skill diagnoses resource exhaustion by analyzing container health checks and correlating crash logs with OOM termination events.

Yes, you can troubleshoot multi-stage build issues and Compose startup-order bugs by inspecting build logs and health check statuses. This Skill diagnoses build failures and validates startup sequences to ensure deployed Compose services initialize dependencies correctly.

Yes, you need Docker CLI access to inspect running or stopped containers and execute debugging commands. This Skill requires local or deployed Docker CLI access to perform log analysis, exec access, and network troubleshooting workflows.

The best way to diagnose a Docker container that never becomes healthy is to review its health check configuration and application logs. This Skill investigates health check failures by validating startup logic, checking resource limits, and analyzing runtime errors.