
Docker Compose Stack Doctor
Diagnose why your Docker Compose stack won't come up: port conflicts, bad or missing env vars, absent healthchecks, volume and permission issues, depends_on that doesn't wait for readiness, networking gaps, platform mismatches, and databases that aren't ready. Reads your docker-compose.yml and logs and ranks the blockers with fixes.
- Resolve service communication and networking mapping errors
- Fix port conflicts and "address already in use" failures
- Debug failing container healthchecks and depends_on dependencies
$15
· or 75 creditsSecure checkout via Stripe
Included in download
- Resolve service communication and networking mapping errors
- Fix port conflicts and "address already in use" failures
- terminal, file_read automation included
- Ready for Works with Claude Code
Sample input
My docker-compose stack isn't starting. The database seems up but the backend keeps crashing with a connection error. Here are my logs and yaml.
Sample output
### Confirmed Findings - **Severity: High** - **Issue:** Backend service attempting to connect to `localhost:5432` instead of `db:5432`. - **Evidence:** Backend logs line 42: `Connection refused: localhost:5432`. - **Fix:** Update `DB_HOST` in `.env` from `localhost` to `db`. - **Verification:** Run `docker-compose up backend`.

Docker Compose Stack Doctor
Diagnose why your Docker Compose stack won't come up: port conflicts, bad or missing env vars, absent healthchecks, volume and permission issues, depends_on that doesn't wait for readiness, networking gaps, platform mismatches, and databases that aren't ready. Reads your docker-compose.yml and logs and ranks the blockers with fixes.
$15
· or 75 creditsSecure checkout via Stripe
Included in download
- Resolve service communication and networking mapping errors
- Fix port conflicts and "address already in use" failures
- terminal, file_read automation included
- Ready for Works with Claude Code
- Instant install
Sample input
My docker-compose stack isn't starting. The database seems up but the backend keeps crashing with a connection error. Here are my logs and yaml.
Sample output
### Confirmed Findings - **Severity: High** - **Issue:** Backend service attempting to connect to `localhost:5432` instead of `db:5432`. - **Evidence:** Backend logs line 42: `Connection refused: localhost:5432`. - **Fix:** Update `DB_HOST` in `.env` from `localhost` to `db`. - **Verification:** Run `docker-compose up backend`.
About This Skill
The Ultimate Diagnostic Tool for Docker Compose
Stop wasting hours chasing "Exited (1)" errors and networking ghosts. The Docker Compose Stack Doctor is a specialized diagnostic skill designed for developers who need to fix broken local environments fast. It provides a structured, evidence-led workflow to identify why your containers won't start, why services can't talk to each other, or why your volumes aren't persisting data.
What it does
This skill goes beyond simple error log reading. It implements a rigorous "evidence-first" devops workflow using a bundled heuristic scanner and comprehensive audit checklists. It analyzes your YAML files, logs, and environment configurations to pinpoint issues across:
- Networking & Ports: Identifies port conflicts and
depends_onreadiness failures. - Environment & Secrets: Finds missing variables and platform/architecture mismatches.
- Storage: Diagnoses volume permission issues and mount paths.
- Runtime: Evaluates healthcheck logic and database readiness.
Why use this skill?
Unlike a general LLM that might hallucinate fixes or suggest dangerous commands, this skill follows a safety-first protocol. It explicitly separates confirmed findings from hypotheses, cites exact evidence for every claim, and provides safe, copy-paste remediation snippets. It includes a local read-only scanner to ensure findings are grounded in your actual project state, not just general advice.
The Output
You receive a professional diagnostic report ranked by severity (Critical to Info). Each finding includes the evidence found, the impact on your stack, a safe remediation snippet, and concrete verification steps to ensure the fix actually worked.
Use Cases
- Resolve service communication and networking mapping errors
- Fix port conflicts and "address already in use" failures
- Debug failing container healthchecks and depends_on dependencies
- Identify misconfigured volumes and file permission mismatches
- Validate environment variables and DB readiness sequences
Known Limitations
- Reads the compose files and logs you provide, not your running daemon or live containers. - Heuristic scanner flags review targets; it does not prove the stack will start. - The bundled clean fixture still surfaces one review item by design; the scanner flags constructs for review, not only outright errors.
How to Install
mkdir -p ~/.claude/skills && curl -sL https://www.agensi.io/api/install/docker-compose-stack-doctor -o /tmp/docker-compose-stack-doctor.zip && unzip -o /tmp/docker-compose-stack-doctor.zip -d ~/.claude/skills && rm /tmp/docker-compose-stack-doctor.zipFree skills install directly. Paid skills require purchase - use the download button above after buying.
Reviews
No reviews yet - be the first to share your experience.
Only users who have downloaded or purchased this skill can leave a review.
Early access skill
Be the first to review this skill.
Only users who have downloaded or purchased this skill can leave a review.
Security Scanned
Passed automated security review
Permissions
File Scopes
Read-only inspection first. The bundled scanner reads matching compose files and logs and prints markdown or JSON findings. It installs nothing, transmits nothing, and modifies nothing. It does not connect to your running Docker daemon. Any write, install, deploy, or live-account action requires explicit user confirmation.
Works with Claude Code, Codex CLI, Cursor, OpenCode/OpenClaw, Gemini CLI, and other agents that load SKILL.md folders. The bundled scanner uses the Python 3 standard library only and degrades to manual checklist mode when Python or matching files are unavailable.