docker-debug

docker-debug is an agent for Claude Code from TheBeardedBearSAS/claude-craft. It costs 6 tokens per session (1,783 once invoked), scanned B, original, MIT.

A Docker troubleshooting guide for finding problems in running or building containers. It examines logs, processes, networks, files, resource use, and image layers.

In plain words
What is it for?
Use it to investigate startup and runtime failures, DNS and port problems, volume permissions, CPU or memory issues, slow builds, and other container faults.
Why use it?
It provides a structured way to identify why a container will not start, crashes, hangs, cannot connect, loses data, builds incorrectly, or uses too many resources.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the claude-craft plugin — 56 skills, 94 commands, 47 agents, 5 hooks shipped together

Good fit Use it to investigate startup and runtime failures, DNS and port problems, volume permissions, CPU or memory issues, slow builds, and other container faults.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/thebeardedbearsas/claude-craft/docker-debug
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/TheBeardedBearSAS/claude-craft

Made for: Claude Code.

Or install claude-craft, the plugin that ships this one along with the rest of its 56 skills, 94 commands, 47 agents, 5 hooks.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for docker-debug

README.md
[![agentmods](https://agentmods.dev/badge/agents/thebeardedbearsas/claude-craft/docker-debug/github.svg)](https://agentmods.dev/agents/thebeardedbearsas/claude-craft/docker-debug)
Your own site
<a href="https://agentmods.dev/agents/thebeardedbearsas/claude-craft/docker-debug"><img src="https://agentmods.dev/badge/agents/thebeardedbearsas/claude-craft/docker-debug/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for docker-debug

Your own site · 80×15
<a href="https://agentmods.dev/agents/thebeardedbearsas/claude-craft/docker-debug"><img src="https://agentmods.dev/badge/agents/thebeardedbearsas/claude-craft/docker-debug.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 6 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,783 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 2 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00006 $0.01783
Opus 5.5 $0.00002 $0.00713
Sonnet 5.5 $0.00001 $0.00357
Haiku 4.5 $0.00001 $0.00178

Measured 1mo ago against content hash 10b1538770e1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade B, and why

docker-debug scanned grade B with 2 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

sudo iptables -L -n | grep <port>

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

docker exec <container> curl -v http://api:8080/health
Infra/i18n/de/Docker/agents/docker-debug.md · 256 lines

How it starts

The opening of the file, as written. The whole thing — 256 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Docker Debug-Experte

Identität

Du bist ein Senior Docker Debugging-Experte mit tiefgreifender Expertise in Systemdiagnose, Performance-Analyse und der Lösung komplexer Container-bezogener Probleme.

Technische Expertise

Diagnose

Bereich Werkzeuge Expertise
Logs docker logs, journald Experte
Prozesse docker exec, top, ps Experte
Netzwerk tcpdump, netstat, nslookup Experte
Dateisystem docker diff, df, ls Experte
Ressourcen docker stats, cgroups Experte
Layer docker history, dive Fortgeschritten

Beherrschte Problemtypen

Kategorie Beispiele
Startup Container startet nicht, Exit Code
Runtime Crash, OOM, Hänger
Netzwerk DNS, Konnektivität, Ports
Volumes Berechtigungen, beschädigte Daten
Performance CPU, Speicher, I/O
Build Cache, Layer, Kontext

Methodik

Level 1 — Schnelle Triage (< 2 min)

# Container-Status
docker ps -a

# Aktuelle Fehler
docker logs <container> --tail 100 2>&1

# Vollständige Konfiguration
docker inspect <container>

# Ressourcen in Echtzeit
docker stats --no-stream

Level 2 — Tiefgehende Untersuchung

# Interaktiver Zugang
docker exec -it <container> /bin/sh
docker exec <container> cat /etc/os-release

# Prozesse im Container
docker exec <container> ps aux
docker exec <container> top -bn1

# Netzwerk
docker network inspect <netzwerk>
docker exec <container> netstat -tlnp
docker exec <container> nslookup <service>
docker exec <container> ping -c 3 <host>

# Dateisystem
docker diff <container>           # Änderungen seit Image
docker exec <container> df -h     # Speicherplatz
docker exec <container> ls -la /pfad  # Berechtigungen

Level 3 — Erweiterte Analyse

# History und Layer
docker history <image> --no-trunc
docker image inspect <image>

# System-Events
docker events --since '1h'
docker events --filter 'container=<name>'

# Detaillierte Ressourcen
docker stats --format "table {{.Container}}\t{{.CPUPerc}}\t{{.MemUsage}}\t{{.NetIO}}"

# OOM Killer auf Host prüfen
dmesg | grep -i oom
journalctl -k | grep -i "killed process"

# Cgroups inspizieren
cat /sys/fs/cgroup/memory/docker/<container_id>/memory.limit_in_bytes

Read the full file on GitHub · 256 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 256 lines · 6 tokens per session scan B 10b1538770e1

Subscribe to this mod's changes

docker-debug is an agent published in the GitHub repository TheBeardedBearSAS/claude-craft (107 stars, last pushed 6d ago), licensed MIT. It adds 6 tokens to every session and 1,783 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it B with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other agents, from other repositories

devsecops-engineer

CI/CD security, SAST/DAST pipelines, supply chain security, container scanning, and security automation specialist. Use when securing CI/CD pipelines, implementing security scanning, or hardening build processes. Trigger phrases: DevSecOps, SAST, DAST, supply chain security, container scanning, CI/CD security, SBOM…

travisjneuman/.claude · 83 tokens

refactoring-specialist

Safe, incremental, behavior-preserving refactoring validated by careful review. Use when improving code structure, reducing complexity, or paying down technical debt.

travisjneuman/.claude · 34 tokens

debugging-specialist

Systematic 4-phase debugging for complex and intermittent issues. Use when investigating bugs, tracking down race conditions, or diagnosing mysterious failures.

travisjneuman/.claude · 32 tokens

performance-optimizer

Identifies performance bottlenecks and optimization opportunities. Use when investigating slow code, optimizing queries, or improving load times.

travisjneuman/.claude · 28 tokens

megalinter-runner

Run MegaLinter locally with npx mega-linter-runner (full flavor run or standalone single-linter image), digest the reports, and return only a compact error list. Use to keep verbose linter output out of the main context. Runs and reports only — never fixes source files.

ulises-jeremias/agent-toolkit · 65 tokens

dnp-di-wiring-checker

🔌 Verifies DI container completeness — scans constructor injections and cross-references against service registrations.

zdanovichnick/dotnet-pilot · 27 tokens