Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
pluginagentmarketplace avatar

Docker Debugging

  • 26 installs
  • 2 repo stars
  • Updated January 5, 2026
  • pluginagentmarketplace/custom-plugin-docker

docker-debugging is an agent skill that supplies categorized Docker CLI commands for inspecting containers, logs, exec sessions, networks, and disk usage.

About

Docker Debugging Commands Reference is a compact command cheat sheet for solo and indie builders who run services in containers on laptops, CI, or small VPS fleets. It groups everyday Docker workflows into five areas so you do not search Stack Overflow while a deploy is red: container inspection for IDs, ports, and live stats; log analysis with follow, tail, timestamps, and time-bounded since queries; interactive debugging via docker exec for shells and one-off commands; network debugging for DNS, ping, and listening ports; and resource analysis starting with docker system df for disk pressure. The skill does not replace observability stacks—it gives procedural knowledge your coding agent can cite while you pair on incidents. Use it when stdout is empty, health checks fail, or a service cannot reach another container on the compose network. Intermediate familiarity with container IDs and compose service names is assumed.

  • Five reference blocks: container_inspection, log_analysis, interactive_debugging, network_debugging, resource_analysis
  • Inspection shortcuts: inspect, top, stats, and port mappings for a given container ID
  • Log recipes: follow, tail 100 lines, timestamps, and --since windows for incident windows
  • Interactive exec: bash/sh, arbitrary commands, and root exec for permission issues
  • Network checks: network inspect, nslookup, ping, and netstat inside the container

Docker Debugging by the numbers

  • 26 all-time installs (skills.sh)
  • Ranked #384 of 610 Debugging skills by installs in the Skillselion catalog
  • Security screen: HIGH risk (skills.sh audit)
  • Data as of Jul 26, 2026 (Skillselion catalog sync)
npx skills add https://github.com/pluginagentmarketplace/custom-plugin-docker --skill docker-debugging

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs26
repo stars2
Security audit2 / 3 scanners passed
Last updatedJanuary 5, 2026
Repositorypluginagentmarketplace/custom-plugin-docker

What it does

Quick-copy Docker CLI recipes when a developer’s container misbehaves in dev or production.

Who is it for?

Best when you're debugging compose stacks, side projects on Docker Desktop, or single-node production without a dedicated SRE runbook.

Skip if: Skip if you already rely on full APM/tracing with no shell access policy exceptions, or pure Kubernetes-only workflows where kubectl debug replaces docker exec.

When should I use this skill?

A container fails health checks, logs are unclear, or you need exec/network verification on a running Docker workload.

What you get

You get a structured command list to inspect state, stream logs, shell in, and test connectivity so you can isolate the failure faster.

  • Ordered Docker CLI commands for the active incident scenario
  • Log tail/follow commands with time windows for correlation
  • In-container network and process checks to narrow root cause

By the numbers

  • 5 command reference categories: inspection, logs, exec, network, resources

Files

SKILL.mdMarkdownGitHub ↗

Docker Debugging Skill

Master container debugging and troubleshooting for development and production issues.

Purpose

Diagnose and resolve container issues including crashes, performance problems, networking failures, and resource constraints.

Parameters

ParameterTypeRequiredDefaultDescription
containerstringNo-Container name/ID
issue_typeenumNo-crash/network/resource/health
verbosebooleanNofalseDetailed output

Debugging Commands

Container Logs

# 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>

Interactive Debugging

# 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

Container Inspection

# 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>

Issue Diagnosis

Container Won't Start

# 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

Exit Code Reference

CodeMeaningAction
0SuccessNormal exit
1General errorCheck logs
137OOMKilledIncrease memory
139SegfaultCheck app code
143SIGTERMGraceful shutdown

Health Check Failures

# 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

Resource Issues

# 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>

Network Issues

# 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>

Troubleshooting Flowchart

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

Debug Container

# Run debug container in same network
docker run --rm -it --network <network> \
  nicolaka/netshoot

# Available tools: curl, dig, nmap, tcpdump, etc.

Error Handling

Common Errors

ErrorCauseSolution
container not foundWrong name/IDUse docker ps -a
exec failedContainer stoppedStart container first
no such fileMissing binaryUse correct image

Usage

Skill("docker-debugging")

Assets

  • assets/debug-commands.yaml - Command reference
  • scripts/container-health-check.sh - Health check script

Related Skills

  • docker-production
  • docker-networking

Related skills

How it compares

Use as a procedural CLI playbook instead of asking the agent to improvise docker commands from memory.

FAQ

Who is docker-debugging for?

Developers and small teams shipping containerized apps who want copy-paste Docker debugging steps during incidents or local dev failures.

When should I use docker-debugging?

In Operate when containers crash-loop or miss dependencies; in Ship when CI-built images fail smoke tests; in Build when compose networking blocks API calls between services.

Is docker-debugging safe to install?

It is reference documentation for powerful host and container commands—review the Security Audits panel on this page and restrict exec/root usage on production systems.

Debuggingdeployinframonitoring

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.