Container Debugging

by aj-geddes3f5182cfd739No license355 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 7 months ago

Debug Docker containers and containerized applications. Diagnose deployment issues, container lifecycle problems, and resource constraints.

Includes scriptsDevOps & Cloud
AI-generated overview

Diagnoses Docker and containerized application problems such as startup failures, crashes, resource limits and networking issues.

What it does
Provides a structured workflow for debugging Docker containers and containerized applications, covering container status checks, log inspection, exec sessions, resource usage and configuration review. It ships reference guides on Docker debugging basics, common container issues, optimization and a debugging checklist, plus a config validation script and a starter configuration template. Output is diagnostic guidance and validated configuration rather than application code.
When to use it
Use when a container will not start, an application crashes inside a container, resource limits are exceeded, or containers show network or performance problems. Also useful when reviewing container configuration before or after deployment.
Requirements
Requires Docker tooling and access to the container runtime to run commands such as docker ps, logs, exec, inspect and stats. Ships an executable validation script and a YAML configuration template.

Container Debugging

Table of Contents

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:

bash
# Check container statusdocker ps -adocker inspect <container-id>docker stats <container-id>
# View container logsdocker logs <container-id>docker logs --follow <container-id>  # Real-timedocker logs --tail 100 <container-id>  # Last 100 lines
# Connect to running containerdocker exec -it <container-id> /bin/bashdocker exec -it <container-id> sh
# Inspect container detailsdocker inspect <container-id> | grep -A 5 "State"docker inspect <container-id> | grep -E "Memory|Cpu"
# Check container processesdocker top <container-id>
# View resource usagedocker stats <container-id># Shows: CPU%, Memory usage, Network I/O
// ... (see reference guides for full implementation)

Reference Guides

Detailed implementations in the references/ directory:

GuideContents
Docker Debugging Basics [blocked]Docker Debugging Basics
Common Container Issues [blocked]Common Container Issues
Container Optimization [blocked]Container Optimization
Debugging Checklist [blocked]Debugging Checklist

Best Practices

✅ DO

  • Follow established patterns and conventions
  • Write clean, maintainable code
  • Add appropriate documentation
  • Test thoroughly before deploying

❌ DON'T

  • Skip testing or validation
  • Ignore error handling
  • Hard-code configuration values

Source and attribution

Source:aj-geddes/useful-ai-promptsinskills/container-debuggingat commit3f5182c

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

Container Debugging Agent Skill | SourceWeft