How do I fix a container with exit code 137?

Exit code 137 usually indicates an Out of Memory (OOM) kill. This skill provides commands to verify OOM status via docker inspect and guidance on adjusting memory limits or optimizing the application.

What is the 4-phase debugging methodology?

It is a structured approach that moves from Quick Assessment (status/logs) and Log Analysis to Interactive Investigation (shells/exec) and Deep Analysis (system events/filesystem exports).

How do I debug a minimal container image without a shell?

This skill suggests using a sidecar approach, such as running a busybox or netshoot container within the same PID or network namespace as the target container for debugging.

Does it cover Docker image build failures?

Yes, it provides troubleshooting steps for common build issues like failed layers, missing files in build contexts, and permission issues during the docker build process.

Can this skill help with networking between containers?

Yes, it includes specific commands for inspecting networks, testing DNS resolution between containers, and using diagnostic tools like netshoot for connectivity analysis.

Docker Debugging Assistant

Name: Docker Debugging Assistant
Author: SnakeO

bySnakeO

0•

デプロイメントとDevOps

Provides a systematic four-phase methodology to diagnose and resolve Docker container, image, networking, and infrastructure issues.

This skill equips Claude with a comprehensive diagnostic framework for troubleshooting Docker environments, ranging from quick status checks to deep-dive forensic analysis of container filesystems. It covers common pitfalls like OOM kills (Exit Code 137), networking isolation problems, volume mount permission errors, and image build failures. By following a structured four-phase methodology—Assessment, Log Analysis, Investigation, and Deep Analysis—it ensures developers can pinpoint root causes efficiently using essential Docker commands and advanced sidecar debugging techniques.

主な機能

01Diagnostic strategies for persistent volume mounts and file system permissions

02Four-phase systematic debugging workflow for rapid problem resolution

03Comprehensive guide to Docker exit codes and their specific root causes

04Resolution patterns for OOM kills and container resource constraints

05Advanced networking and connectivity troubleshooting for container communication

060 GitHub stars

ユースケース

01Troubleshooting a container that keeps restarting with a mysterious exit code 137

02Diagnosing network connectivity failures between microservices in a Docker bridge network

03Fixing 'Permission Denied' errors in volume mounts across different host operating systems

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add snakeo/claude-debug-and-refactor-skills-plugin debug-docker

For use in Claude.ai and ChatGPT

Download Skill