How do I install the Ksopyla Agent Patterns Lab Docker Debugger skill?

Run npx skillmds@latest add tomevault-io/ksopyla-agent-patterns-lab-docker-debugger in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Ksopyla Agent Patterns Lab Docker Debugger skill do?

Docker Debugger It is listed under DevOps & Infra on SkillMD.

Is Ksopyla Agent Patterns Lab Docker Debugger safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ksopyla Agent Patterns Lab Docker Debugger?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ksopyla Agent Patterns Lab Docker Debugger free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ksopyla Agent Patterns Lab Docker Debugger?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ksopyla Agent Patterns Lab Docker Debugger by tomevault-io

Name: Ksopyla Agent Patterns Lab Docker Debugger
Author: tomevault-io

File contents

Docker Debugger

When to Use

Trigger this skill when:

docker compose up --build fails or a container exits unexpectedly
An agent service can't reach another service (network/DNS issues)
Debugging multi-container setups in Patterns 05+
Investigating image build failures with the base Dockerfile

Available MCP Tools

Use the Docker MCP (project-0-agent-patterns-lab-docker) for inspection:

Tool	Purpose
`list_containers`	See running/stopped containers and their status
`fetch_container_logs`	Read stdout/stderr from a specific container
`list_images`	Check built images and tags
`list_networks`	Inspect Docker networks for multi-service setups
`list_volumes`	Check persistent volumes (PostgreSQL, etc.)
`start_container` / `stop_container`	Control individual containers
`recreate_container`	Rebuild and restart a single container

Diagnostic Workflow

Check container status
- Call list_containers to see which containers are running, exited, or restarting
- Note exit codes: 0 = clean stop, 1 = app error, 137 = OOM killed
Read logs for the failing container
- Call fetch_container_logs with the container name
- Look for: import errors, missing env vars, port conflicts, connection refused
Verify network connectivity (multi-service)
- Call list_networks to confirm all services share a network
- Service DNS names match the services: keys in docker-compose.yml
- Common fix: services on different networks can't reach each other
Check image build
- Call list_images to verify the image was built
- If missing, the build stage likely failed -- re-read build logs
Fix and rebuild
- Fix the issue in code or config
- Run docker compose up --build to rebuild

Project-Specific Build Context

All examples use the base Dockerfile at infra/docker/base/Dockerfile.agent:

Build context is always the repo root (../.. from the example)
Compose sets PACKAGE_NAME, EXAMPLE_PYPROJECT, and EXAMPLE_SRC for that example
Multi-stage build: builder installs deps, runtime copies artifacts
.env file is passed via env_file in docker-compose

Common Failures

Symptom	Likely Cause	Fix
`ModuleNotFoundError`	Dependency missing in `pyproject.toml`	`uv add <package>` in the example, rebuild
`Connection refused` on port 8000	App not binding to `0.0.0.0`	Set `--host 0.0.0.0` in uvicorn command
Container restarts in loop	Crash on startup (missing env var)	Check `.env` file, compare with `.env.example`
`network X not found`	Compose network not created	Run `docker compose down` then `up` again
Build fails at `uv sync`	Lock file out of sync	Run `uv lock` locally first, then rebuild

Shell Commands (PowerShell)

# Build and run from example directory
docker compose up --build

# Rebuild single service
docker compose up --build agent

# View logs for a service
docker compose logs -f agent

# Full reset (remove containers, networks, volumes)
docker compose down -v

Source: ksopyla/agent-patterns-lab — distributed by TomeVault.

---name: ksopyla-agent-patterns-lab-docker-debuggerdescription: Docker Debugger---# Docker Debugger## When to UseTrigger this skill when:- `docker compose up --build` fails or a container exits unexpectedly- An agent service can't reach another service (network/DNS issues)- Debugging multi-container setups in Patterns 05+- Investigating image build failures with the base Dockerfile## Available MCP ToolsUse the Docker MCP (`project-0-agent-patterns-lab-docker`) for inspection:| Tool | Purpose ||------|---------|| `list_containers` | See running/stopped containers and their status || `fetch_container_logs` | Read stdout/stderr from a specific container || `list_images` | Check built images and tags || `list_networks` | Inspect Docker networks for multi-service setups || `list_volumes` | Check persistent volumes (PostgreSQL, etc.) || `start_container` / `stop_container` | Control individual containers || `recreate_container` | Rebuild and restart a single container |## Diagnostic Workflow1. **Check container status** - Call `list_containers` to see which containers are running, exited, or restarting - Note exit codes: `0` = clean stop, `1` = app error, `137` = OOM killed2. **Read logs for the failing container** - Call `fetch_container_logs` with the container name - Look for: import errors, missing env vars, port conflicts, connection refused3. **Verify network connectivity** (multi-service) - Call `list_networks` to confirm all services share a network - Service DNS names match the `services:` keys in `docker-compose.yml` - Common fix: services on different networks can't reach each other4. **Check image build** - Call `list_images` to verify the image was built - If missing, the build stage likely failed -- re-read build logs5. **Fix and rebuild** - Fix the issue in code or config - Run `docker compose up --build` to rebuild## Project-Specific Build ContextAll examples use the base Dockerfile at `infra/docker/base/Dockerfile.agent`:- Build context is always the repo root (`../..` from the example)- Compose sets `PACKAGE_NAME`, `EXAMPLE_PYPROJECT`, and `EXAMPLE_SRC` for that example- Multi-stage build: `builder` installs deps, `runtime` copies artifacts- `.env` file is passed via `env_file` in docker-compose## Common Failures| Symptom | Likely Cause | Fix ||---------|-------------|-----|| `ModuleNotFoundError` | Dependency missing in `pyproject.toml` | `uv add <package>` in the example, rebuild || `Connection refused` on port 8000 | App not binding to `0.0.0.0` | Set `--host 0.0.0.0` in uvicorn command || Container restarts in loop | Crash on startup (missing env var) | Check `.env` file, compare with `.env.example` || `network X not found` | Compose network not created | Run `docker compose down` then `up` again || Build fails at `uv sync` | Lock file out of sync | Run `uv lock` locally first, then rebuild |## Shell Commands (PowerShell)```powershell# Build and run from example directorydocker compose up --build# Rebuild single servicedocker compose up --build agent# View logs for a servicedocker compose logs -f agent# Full reset (remove containers, networks, volumes)docker compose down -v```---> Source: [ksopyla/agent-patterns-lab](https://github.com/ksopyla/agent-patterns-lab) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions

Ksopyla Agent Patterns Lab Docker Debugger