troubleshoot-docker

Diagnose Docker infrastructure failures using Netdata MCP health signals.

1|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/netdata/skills --skill troubleshoot-docker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: troubleshoot-docker
Source: https://github.com/netdata/skills/tree/main/skills/troubleshoot-docker
Command: npx skills add https://github.com/netdata/skills --skill troubleshoot-docker

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Troubleshoot disruptive Docker outages by identifying the failure archetype and guiding targeted remediation instead of guessing from generic health checks.

Core Features & Use Cases

  • Docker incident triage for disk exhaustion, OOM cascades, daemon hangs/lockups, log explosions, and network isolation failures.
  • Netdata MCP-based signal querying to verify container and host symptoms across the relevant Netdata Docker contexts.
  • Operator playbook-aligned diagnostic tree that recommends next actions and re-checks whether signals return to expected bands.
  • Use Case: When a production host starts failing container operations after disk growth, use this skill to confirm the pattern via Netdata and drive the remediation with verification.

Quick Start

Ask the agent: troubleshoot my Docker incident by querying Netdata via MCP and walking the diagnostic tree to recommend the most likely remediation.

Frequently Asked Questions about troubleshoot-docker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I troubleshoot Docker daemon hangs and lockups during an incident?

Troubleshoot Docker daemon hangs by matching symptoms to operator playbook failure archetypes and verifying them with Netdata MCP Docker health signals to guide targeted remediation.

What is the best way to diagnose Docker OOM cascades and disk exhaustion?

Diagnose Docker OOM cascades and disk exhaustion by querying Netdata MCP docker.* contexts to find anomalies and check correlated signals against expected bands.

How do I verify Docker container recovery after applying incident remediation?

Verify Docker container recovery by running post-remediation Netdata MCP queries to confirm that health signals return to expected bands within a defined window.

Can I use Netdata MCP to detect Docker log explosions and shim leaks?

Yes, you can use Netdata MCP to query docker.* contexts and detect Docker log explosions and shim leaks by applying operator playbook-aligned diagnostic trees.

Does this Docker troubleshooting approach handle network isolation failures?

Yes, this Docker troubleshooting approach handles network isolation failures by matching symptoms to failure archetypes and verifying them with Netdata MCP Docker health signals.