incidentfox Docker Debugging
Authentication
Docker commands run directly via the Docker CLI. No API keys are needed - the Docker socket must be accessible in the sandbox environment.
Available Scripts
All scripts are in .claude/skills/infrastructure-docker/scripts/
container_ps.py - List Containers
python .claude/skills/infrastructure-docker/scripts/container_ps.py [--all]
container_logs.py - Get Container Logs
python .claude/skills/infrastructure-docker/scripts/container_logs.py --container NAME_OR_ID [--tail 100]
container_inspect.py - Inspect Container
python .claude/skills/infrastructure-docker/scripts/container_inspect.py --container NAME_OR_ID
container_stats.py - Resource Usage Statistics
python .claude/skills/infrastructure-docker/scripts/container_stats.py [--container NAME_OR_ID]
image_list.py - List Docker Images
python .claude/skills/infrastructure-docker/scripts/image_list.py [--filter "reference=myapp*"]
compose_ps.py - List Compose Services
python .claude/skills/infrastructure-docker/scripts/compose_ps.py [--file docker-compose.yml] [--cwd /path]
compose_logs.py - Get Compose Service Logs
python .claude/skills/infrastructure-docker/scripts/compose_logs.py [--services "api,db"] [--tail 100]
Investigation Workflow
Container Debugging
1. List containers: container_ps.py --all
2. Check logs: container_logs.py --container <name> --tail 200
3. Check resources: container_stats.py --container <name>
4. Inspect config: container_inspect.py --container <name>
Docker Compose Debugging
1. Check services: compose_ps.py
2. Check logs: compose_logs.py --services "api,worker" --tail 100
Anti-Patterns to Avoid
- Never run destructive commands without explicit user approval (docker rm, docker rmi, docker system prune)
- Always use --tail for logs to avoid overwhelming output
- Check container status first before trying to exec into it