docker-troubleshoot

Docker container startup failures stem from configuration errors, permission issues, or resource conflicts. Use Docker logs and inspect commands to review error messages, then check your YAML configuration, volume permissions, and port availability to identify and resolve the root cause.

Port conflicts occur when multiple containers or services bind to the same port. Inspect running containers to identify which process occupies the port, then either reassign the conflicting service to a different port in your Docker Compose configuration or stop the competing container.

Docker networking issues typically involve DNS resolution, service discovery, or network isolation. Inspect container logs, verify service names in your Docker Compose configuration, check network connectivity between containers, and confirm firewall rules and container network settings align with your deployment topology.

Volume issues prevent data persistence across container restarts. Verify volume mount paths in your YAML configuration match actual directories, check file permissions for read/write access, and inspect mounted volumes to confirm data is being written to the correct locations.

Health check failures indicate containers aren't responding to liveness probes. Review health check configuration in your Docker Compose file, inspect container logs for startup delays or dependency issues, and verify the health check endpoint or command is accessible and returns expected responses.

Yes, this Skill covers both Docker Compose and standalone Docker deployments. It handles startup failures, networking problems, permission errors, and port conflicts across both deployment models, requiring Docker CLI access and read/write permissions to configuration files.