Container Debugging

This handles the standard Docker debugging workflow: checking container status, tailing logs, exec'ing into running containers, and inspecting resource usage. You'd reach for it when containers won't start, crash unexpectedly, or hit resource limits. The quick start covers the essential commands you actually use (docker ps, logs, inspect, exec, stats), which is 90% of container debugging in practice. It includes reference guides for common issues and optimization patterns. Honestly, if you work with containers regularly, you probably have most of these commands memorized already, but having them organized in one place with a structured troubleshooting approach is solid for onboarding teammates or when you hit something unfamiliar.

skills.sh installs: 494
GitHub stars: 379
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add aj-geddes/useful-ai-prompts --skill container-debugging --agent claude-code

Installs into .claude/skills of the current project.

Files

Overview

Container debugging focuses on issues within Docker/Kubernetes environments including resource constraints, networking, and application runtime problems.

When to Use

Container won't start
Application crashes in container
Resource limits exceeded
Network connectivity issues
Performance problems in containers

Quick Start

Minimal working example:

# Check container status
docker ps -a
docker inspect <container-id>
docker stats <container-id>

# View container logs
docker logs <container-id>
docker logs --follow <container-id>  # Real-time
docker logs --tail 100 <container-id>  # Last 100 lines

# Connect to running container
docker exec -it <container-id> /bin/bash
docker exec -it <container-id> sh

# Inspect container details
docker inspect <container-id> | grep -A 5 "State"
docker inspect <container-id> | grep -E "Memory|Cpu"

# Check container processes
docker top <container-id>

SKILL.md on GitHub