Docker Internals

Use when the user asks how containers work, Linux namespaces and cgroups v2, OverlayFS layers and copy-on-write, containerd and runc, the OCI runtime spec, container PID 1 and signals, or why a container is OOM killed. Explains container primitives for debugging and hardening. Not for Dockerfile authoring (use docker-patterns) or image scanning (use security-container-security).

45 stars 6 forksDevOps & Cloud

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add j4flmao/agent-skills --skill docker-internals
Manual install
git clone --depth 1 https://github.com/j4flmao/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/devops/orchestration/docker-internals ~/.claude/skills/docker-internals

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Docker and Container Internals

## Purpose
A container is an ordinary Linux process tree started with isolated namespaces, constrained by cgroups, with reduced privileges, and a root filesystem assembled from image layers. Knowing this explains OOM kills, PID 1 signal problems, file-change behaviour, and what "privileged" really grants.

## Agent Protocol

### Trigger
"how do containers work", "docker internals", "namespaces", "cgroups", "overlayfs", "copy on write", "containerd", "runc", "OCI runtime", "PID 1", "OOM killed".

### Input Context
- Host OS/kernel, cgroup version (`stat -fc %T /sys/fs/cgroup` → `cgroup2fs` means v2).
- Runtime (Docker Engine, containerd via Kubernetes, Podman).
- Symptom being debugged.

### Output Artifact
Explanation + inspection commands + fix. No file unless requested.

### Response Format
```
Mechanism: {namespace|cgroup|capability|seccomp|overlayfs|runtime}
Evidence: {commands and expected output}
Explanation: {...}
Fix: {run flags / Dockerfile / K8s field}
```

### Completion Criteria
- [ ] Symptom mapped to a specific kernel mechanism.
- [ ] Inspection commands given to confirm.

## Runtime Stack
```mermaid
flowchart LR
  CLI[docker CLI] --> D[dockerd]
  D --> C[containerd]
  C --> S[containerd-shim-runc-v2]
  S --> R[runc: creates namespaces/cgroups, execs process]
  K[kubelet] -->|CRI gRPC| C
```
- Images and runtimes follow the OCI Image and Runtime specs; any OCI image runs on containerd/CRI-O/Podman.
Read the full skill on GitHub

Details

Skill name
docker-internals
Path
skills/devops/orchestration/docker-internals/SKILL.md
License
MIT
Repo updated
17 November 2026

FAQ

What does the Docker Internals skill do?

Use when the user asks how containers work, Linux namespaces and cgroups v2, OverlayFS layers and copy-on-write, containerd and runc, the OCI runtime spec, container PID 1 and signals, or why a container is OOM killed. Explains container primitives for debugging and hardening. Not for Dockerfile authoring (use docker-patterns) or image scanning (use security-container-security).

How do I install the Docker Internals skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add j4flmao/agent-skills --skill docker-internals. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Docker Internals popular?

It lives in j4flmao/agent-skills, which has 45 GitHub stars and 6 forks.

Related skills

Agent Observability

45

j4flmao/agent-skills

Use when the user asks about agent observability, tracing agent reasoning, debugging an agent loop, OpenTelemetry GenAI spans for LLM calls, LLM cost tracking per agent, agent audit logs or hallucination/eval monitoring in production. Produces instrumentation config, trace schema, dashboards, alerts and cost attribution. Not for generic service tracing without LLMs (use devops-opentelemetry).

DevOps & Cloud

AI Agent Architectures

45

j4flmao/agent-skills

Use when the user asks to build an AI agent, design an agent that calls tools and keeps memory, write an agent system prompt or pick an agent framework (Claude Agent SDK, OpenAI Agents SDK, LangGraph). Produces an architecture brief covering loop, tools, memory, guardrails and evals, routing depth to child skills. Not for workflow patterns (use ai-agentic-workflows).

AI, LLMs & Agents

AI Agent Core Loop

45

j4flmao/agent-skills

Use when the user asks about the agent loop, ReAct vs plan-and-solve, re-planning, Reflexion, an agent stuck in a loop, max iterations or termination conditions. Produces a loop spec or patch with state, success predicate, caps and no-progress detection. Not for overall agent design (use ai-agent-architectures) or tool schemas (use tool-calling-principles).

AI, LLMs & Agents

Docker Patterns

45

j4flmao/agent-skills

Use when the user asks to write a Dockerfile, a multi-stage Dockerfile for a Node, Python or Go service, Docker Compose, .dockerignore, non-root containers, layer caching, BuildKit cache mounts, or image healthchecks. Produces small, secure Dockerfiles and Compose files. Not for container internals like cgroups (use docker-internals) or Kubernetes manifests (use cloud-native-kubernetes-patterns).

DevOps & Cloud

Digitalocean

45

j4flmao/agent-skills

Use when the user asks about DigitalOcean, Droplets, DOKS, App Platform, Spaces, managed databases, reserved IPs, cloud firewalls, doctl, or the Terraform digitalocean provider. Produces DigitalOcean infrastructure and IaC. Not for AWS (use aws) or Hetzner (use hetzner-cloud).

DevOps & Cloud

Enterprise Cost Governance

45

j4flmao/agent-skills

Use when the user asks about cloud cost governance: tagging policy, cost allocation, showback or chargeback, budgets and alerts, cost anomaly detection or unit cost reporting. Produces a cost governance model with owners and controls. Not for hands-on cloud cost optimization (use devops-finops) or capacity forecasts (use enterprise-capacity-planning).

DevOps & Cloud

Browse the most popular Claude skills, all devops & cloud skills, or write your own with the skills generator.