skills.rest
incidentfox
incidentfoxOFFICIAL
Explore all skills by this author →
WebsiteGitHub

docker-debugging

Inspect Docker containers, logs, images, and Compose services for debugging.

656|82|Updated Jan 20, 2026
Search Tags:#logs#docker#containers#docker compose#Debugging#devOps#Incident Investigation
One-click install
npx skills add https://github.com/incidentfox/incidentfox --skill docker-debugging
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: docker-debugging
Source: https://github.com/incidentfox/incidentfox/tree/main/sre-agent/.claude/skills/infrastructure-docker
Command: npx skills add https://github.com/incidentfox/incidentfox --skill docker-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Diagnosing container issues requires running many Docker CLI commands and parsing their output manually, which slows down incident investigation and risks accidental destructive operations.

Core Features & Use Cases

  • Container Inspection: List containers, fetch logs with tail limits, inspect configuration, and view CPU, memory, network, and block I/O statistics.
  • Docker Compose Support: List Compose services and retrieve per-service logs for multi-container applications.
  • Safe Read-Only Execution: A shared runner blocks destructive subcommands like rm, prune, kill, and exec, and redacts sensitive environment variables such as passwords and tokens from inspect output.
  • Use Case: When a container keeps restarting in production, list all containers, pull the last 200 log lines, check resource usage, and inspect its configuration to find the root cause without leaving the chat.

Quick Start

Use the docker-debugging skill to list all containers and show the last 100 log lines for the failing api container.

Frequently Asked Questions about docker-debugging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug a failing Docker container?▼

Start by listing containers with container_ps.py --all, then pull recent logs with container_logs.py --container NAME --tail 200. Follow up with container_stats.py for resource usage and container_inspect.py for configuration details.

How do I check Docker Compose service logs?▼

Run compose_ps.py to list services in your Compose file, then use compose_logs.py --services "api,db" --tail 100 to fetch logs for specific services. You can point to a custom Compose file with the --file flag.

Can this skill delete or stop Docker containers?▼

No. The shared docker_runner blocks destructive subcommands including rm, prune, kill, stop, exec, and build. Only read-only operations like ps, logs, inspect, stats, and images are permitted.

Does container inspect expose secrets in environment variables?▼

No. container_inspect.py redacts environment variables whose keys match sensitive patterns like password, secret, token, or key, and also masks values containing embedded credentials. Raw unredacted output is removed from JSON responses.

What do I need to run these Docker debugging scripts?▼

You need Python 3 and the Docker CLI available in PATH with access to the Docker socket. No API keys or external Python packages are required since the scripts use only the standard library.

Related Skills

Explore More Software Engineering Skills→
NITRR-OfficialNITRR-Official
4

deployment-docker

Automate Docker image creation and Compose configuration for CampusOS.

Official
Intermediate
mattdurhammattdurham
9

error-detective

Analyze logs, traces, and metrics to diagnose root causes across distributed systems.

Community
Advanced
dmzoneilldmzoneill
2

debug-prod

Diagnose production issues by analyzing Kubernetes pods, logs, metrics, alerts, and deployments.

Community
Advanced
eveldeveld
10

k8s-awareness

Debug Kubernetes workloads using structured locator, analyzer, and pattern-finder workflows.

Community
Advanced