From monotemplate
Troubleshoot Docker Compose startup errors. Use when encountering network conflicts, container name collisions, orphaned containers, or other Docker setup issues.
How this skill is triggered — by the user, by Claude, or both
Slash command
/monotemplate:docker-troubleshootThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Error message:**
Error message:
failed to create network: Error response from daemon: invalid pool request: Pool overlaps with other one on this address space
Cause: The subnet defined in docker-compose conflicts with an existing Docker network.
Fix:
docker-compose.dev.ymlnetworks section at the bottom172.28.0.0/16 instead of 172.20.0.0/16)ipv4_address values for each service to match the new subnetAlternative: Clean up unused networks with:
docker network prune
Error message:
Error response from daemon: Conflict. The container name "/container-name" is already in use
Cause: Orphaned containers from a previous run weren't cleaned up properly.
Fix: Remove the conflicting containers:
docker rm -f postgres-dev migrate-dev server-dev web-dev nginx-dev
Or remove all stopped containers:
docker container prune
When Docker state is severely corrupted:
docker stop $(docker ps -aq)
docker rm $(docker ps -aq)
docker network rm caliber-fleet-management_app_network
docker system prune -f
docker ps -a # List all containers
docker network ls # List all networks
docker network inspect <name> # Inspect network subnet
npx claudepluginhub firstloophq/claude-code-plugins --plugin monotemplateDiagnoses Docker container failures, networking issues, permissions errors, port conflicts, data persistence problems, and health checks using docker compose logs, inspect, and targeted fixes.
Configures Docker Compose networks for service communication and isolation, covering default bridge networks, custom bridges, overlay networks, aliases, and service discovery in multi-container apps.
Provides Docker and Docker Compose patterns for local development, container security, networking, volume strategies, and multi-service orchestration.