analyze-local

Docker container diagnostics involves gathering system state, logs, and resource metrics to identify crash causes. This skill automates collecting container health and network configurations, correlating symptoms like OOM kills or port conflicts with failure patterns to pinpoint root causes.

Port conflicts occur when multiple containers attempt to bind the same host port. This skill analyzes local Docker network configurations and container statuses to detect these conflicts, extracting relevant logs to suggest targeted configuration fixes for your development workflow.

Yes, you can diagnose Docker performance bottlenecks by analyzing container resource utilization and daemon health. This skill gathers comprehensive snapshots of system metrics, correlating them with common failure patterns to isolate the specific container causing the performance issue.

Yes, you need Docker CLI access and standard shell utilities to execute diagnostic commands. This skill relies on these local environment dependencies to gather container health data, network configurations, and system state for interpreting failures.

Debugging local container connectivity issues requires analyzing Docker network configurations and container statuses. This skill systematically gathers network configurations and relevant logs, correlating them with failure patterns to identify and resolve connectivity issues in your development workflow.