log analyzer docker

Debug Docker infrastructure without manual log scrubbing. This skill parses logs from Docker Engine, Docker Compose, and BuildKit to isolate container failures, daemon connectivity issues, and image build errors. It moves past generic error messages to identify specific root causes like OOM kills, architecture mismatches, and socket permission errors.

What it does

• Diagnose Engine Failures identifies daemon connection errors, socket permission issues, and disk space exhaustion.
• Analyze Compose Services tracks service health dependencies and port allocation conflicts across multi-container setups.
• Troubleshoot BuildKit pinpoints exact Dockerfile line failures, build context mismatches, and registry rate limits.
• Identify Exit Codes interprets system signals such as Exit Code 137 (OOMKilled) or OCI runtime execution errors.
• Detect Security Risks flags exposed credentials in build args, environment variables, or unencrypted registry configs.

How it works

1. Detection scans for Docker-specific markers like docker-compose.yml patterns, dockerd entries, or BuildKit prefixes.
2. Context Gathering asks for missing environment details like host OS, Docker version, or the relevant compose.yaml.
3. Analysis maps log patterns against known failure states like exec format error or dependency failed to start.
4. Reporting generates a structured diagnostic report with critical findings and recommended fixes.

Frameworks & tools

Works with Docker Engine, Docker Compose, BuildKit, and Docker Desktop. It handles logs from standard Linux hosts and amd64/arm64 cross-platform builds.

Why this beats prompting it yourself

Generic prompts often miss low-level Docker signals like Exit Code 137 or docker.sock permission nuances. This skill follows a specialized diagnostic framework that explicitly checks for OOM kills and hidden security leaks in build layers that general models overlook.

Use cases

• Debugging a container that is stuck in a restart loop without obvious application errors.
• Resolving complex Docker Compose startup failures where services fail their healthchecks.
• Fixing failed to solve errors in CI/CD pipelines using BuildKit.
• Auditing Docker logs for sensitive data leaks before moving to production.

Known limitations

Does not support Kubernetes logs (use log-analyzer-kubernetes instead). Requires logs to be provided in text format; cannot directly access local Docker sockets or CLI.