Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Diagnose and fix Docker container issues. Use when a service is not responding, container is in restart loop, or health check fails. Triggers on: docker, container, service down, not responding, restart loop, health check.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-02 | ✗→✓ | ▲ Improved | -39% | 0% |
| case-06 | ✗→✓ | ▲ Improved | -30% | 0% |
| case-20 | ✗→✓ | ▲ Improved | -33% | 0% |
| case-15 | ✗→✓ | ▲ Improved | -39% | 0% |
| case-19 | ✗→✓ | ▲ Improved | 7% | 0% |
bash docker compose ps
bash docker compose logs --tail=50 <service> Common causes: missing env vars, port conflicts, OOM kills.
bash docker compose up -d <service> docker compose logs -f <service> # watch startup
bash docker compose exec <service> sh # get a shell # Check if process is running inside # Check if port is listening netstat -tlnp || ss -tlnp
bash docker stats --no-stream df -h # disk full?
| Symptom | Fix | |---------|-----| | OOM killed | Increase memory limit in compose file | | Port conflict | Check docker compose ps for port bindings, stop conflicting service | | Volume mount error | Verify host path exists: ls -la <path> | | Image not found | docker compose pull <service> | | Config changed | docker compose up -d --force-recreate <service> |
Always verify the service is healthy:
bashdocker compose ps # status should be "Up" curl -s http://localhost:<port>/health # if applicable
Other measured skills in the registry, with their headline benchmark lift.