Menü
Troubleshoot Docker Compose startup errors. Use when encountering network conflicts, container name collisions, orphaned containers, or other Docker setup issues.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Commit, push, open a PR, and monitor CI/CD in a loop. Use when the user says "ship it", "commit push and watch CI", or wants to open a PR and monitor checks. Auto-fixes obvious CI failures and stops to ask for non-obvious ones.
Add and manage integration tests for repositories and API endpoints. Use when adding integration tests, testing a repository, testing an API endpoint, or setting up integration test infrastructure.
Add or modify CRUD entities following the layered architecture pattern with oRPC contracts and Inversify DI. Use when adding new database models, creating API endpoints, or implementing data access layers.
Wire classes into the Inversify DI container correctly. Use when adding new repositories, controllers, services, or middleware to the server. Use when wiring dependencies, configuring the DI container, or understanding how classes are resolved.
Configure the anthropics/claude-code-action GitHub Action correctly. Use when setting up Claude Code workflows, troubleshooting GitHub Action configuration, or passing CLI flags via claude_args.
Create and improve Claude Skills with proper structure, frontmatter, and best practices. Use when creating new skills, improving existing skills, refactoring skill content, or scaffolding skill files.
| name | docker-troubleshoot |
| description | Troubleshoot Docker Compose startup errors. Use when encountering network conflicts, container name collisions, orphaned containers, or other Docker setup issues. |
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