- Home
- Skills
- DevOps & Cloud
- log analyzer docker
log analyzer docker
Analyze Docker Engine, Compose, and BuildKit logs to diagnose container failures, OOM kills, and security leaks.
$1
Works with the AI Agents you already use
log analyzer docker
Example session with this skill installed
Analyze these logs
api-1 | Error: Cannot connect to the database
api-1 | api-1 exited with code 137
db-1 | 2023-10-27 10:00:00 [ERROR] Out of memory.
db-1 | db-1 exited with code 1
docker-compose.yml has ARG DB_PASS=secret123
- Read your context and instructions
- Compiled the log analyzer docker
The logs indicate a resource exhaustion issue leading to a service crash, along with a security risk in your configuration.
REPORTE DE ANÁLISIS DE LOG — DOCKER
| Sección | Detalle |
|---|---|
| Tecnología | Docker Compose / Docker Engine |
| Entorno | No declarado (asumido Local/Dev) |
| Componentes | api-1, db-1 |
| Total eventos | 2 Críticos, 1 Advertencia |
| Diagnóstico | El servicio db-1 sufrió un error de memoria, provocando que api-1 fuera terminado por el kernel (OOM) o el daemon. |
🔴 HALLAZGOS CRÍTICOS
Exit Code 137 (api-1): El contenedor fue terminado forzosamente. Esto suele indicar que el OOM Killer de Docker intervino porque el contenedor superó su límite de memoria asignado.
Database Failure (db-1): El log muestra explícitamente Out of memory. El servicio de base de datos colapsó, lo que causó el error de conexión en la API antes de que esta también fuera terminada.
🟡 ADVERTENCIAS
Seguridad: Se detectó el uso de ARG DB_PASS. Los valores pasados por ARG persisten en el historial de capas de la imagen.
- DATO SENSIBLE: Valor: <span style="color:red;font-weight:bold">secret123</span>
🛠️ PRÓXIMOS PASOS
- Aumentar los límites de memoria en
compose.yamlpara el serviciodb-1usando la clavedeploy.resources.limits.memory. - Migrar
DB_PASSdeARGasecrets:o un archivo.envpara evitar que la credencial quede grabada en la imagen. - Revisar
docker inspect api-1para confirmar siOOMKilledestrue.
¿Deseas el reporte como documento entregable (Word/Markdown)?
Connects securely to your tools. The creator never sees your data.
About this skill
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
- Detection scans for Docker-specific markers like
docker-compose.ymlpatterns,dockerdentries, or BuildKit prefixes. - Context Gathering asks for missing environment details like host OS, Docker version, or the relevant
compose.yaml. - Analysis maps log patterns against known failure states like
exec format errorordependency failed to start. - 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 solveerrors 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.
Does not support Kubernetes logs. Cannot directly access local Docker sockets or run CLI commands. Requires manual log input.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 28 days ago