Container debugging and troubleshooting techniques for production issues
Master container debugging and troubleshooting for development and production issues.
Diagnose and resolve container issues including crashes, performance problems, networking failures, and resource constraints.
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| container | string | No | - | Container name/ID |
| issue_type | enum | No | - | crash/network/resource/health |
| verbose | boolean | No | false | Detailed output |
# Last 100 lines
docker logs --tail 100 <container>
# Follow logs
docker logs -f <container>
# With timestamps
docker logs -t <container>
# Specific time range
docker logs --since 1h --until 30m <container>
# Execute shell in running container
docker exec -it <container> /bin/sh
# As root (for debugging)
docker exec -u 0 -it <container> /bin/sh
# Run command
docker exec <container> ps aux
# Full inspection
docker inspect <container>
# Specific fields
docker inspect --format='{{.State.Status}}' <container>
docker inspect --format='{{.State.Health.Status}}' <container>
docker inspect --format='{{json .NetworkSettings}}' <container>
# Check exit code
docker inspect --format='{{.State.ExitCode}}' <container>
# View last logs
docker logs --tail 50 <container>
# Check events
docker events --filter 'container=<name>' --since 1h
| Code | Meaning | Action |
|---|---|---|
| 0 | Success | Normal exit |
| 1 | General error | Check logs |
| 137 | OOMKilled | Increase memory |
| 139 | Segfault | Check app code |
| 143 | SIGTERM | Graceful shutdown |
# Check health status
docker inspect --format='{{json .State.Health}}' <container>
# View health logs
docker inspect --format='{{range .State.Health.Log}}{{.Output}}{{end}}' <container>
# Manually test health
docker exec <container> curl -f http://localhost/health
# Live stats
docker stats <container>
# Formatted output
docker stats --format "table {{.Name}}\t{{.CPUPerc}}\t{{.MemUsage}}\t{{.NetIO}}"
# Check limits
docker inspect --format='{{.HostConfig.Memory}}' <container>
# Check network
docker network inspect <network>
# Test DNS
docker exec <container> nslookup <service>
# Test connectivity
docker exec <container> ping -c 3 <target>
docker exec <container> curl http://<service>:port
# View ports
docker port <container>
Container Issue?
ā
āā Won't Start
ā āā Check logs: docker logs <c>
ā āā Check exit code: docker inspect
ā āā Verify image: docker pull
ā
āā Unhealthy
ā āā Check health logs
ā āā Test health endpoint manually
ā āā Increase start_period
ā
āā High Resource
ā āā Check stats: docker stats
ā āā Increase limits
ā āā Profile application
ā
āā Network Failed
āā Check DNS: nslookup
āā Check connectivity: ping/curl
āā Verify network membership
# Run debug container in same network
docker run --rm -it --network <network> \
nicolaka/netshoot
# Available tools: curl, dig, nmap, tcpdump, etc.
| Error | Cause | Solution |
|---|---|---|
container not found |
Wrong name/ID | Use docker ps -a |
exec failed |
Container stopped | Start container first |
no such file |
Missing binary | Use correct image |
Skill("docker-debugging")
assets/debug-commands.yaml - Command referencescripts/container-health-check.sh - Health check script