# Insecure Docker Configuration

> Detects dangerous Docker and Docker Compose configurations including privileged containers, secrets in environment variables, and running as root.

- Skill: `zakirkun/insecure-docker-configuration` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add zakirkun/insecure-docker-configuration`
- Raw SKILL.md: https://api.skillmd.com/api/skills/zakirkun/insecure-docker-configuration/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- Author: zakirkun (https://skillmd.com/u/zakirkun)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/zakirkun/insecure-docker-configuration

---


# Insecure Docker Configuration

## Overview
Docker misconfiguration can lead to container escapes and privilege escalation:
1. **`--privileged` flag**: Gives container full host capabilities, enabling container escape
2. **Running as root**: Default behavior — prefer non-root user
3. **Secrets in ENV variables**: Visible via `docker inspect` and process listings
4. **`--cap-add=SYS_ADMIN`**: Grants dangerous capabilities
5. **Mounting Docker socket**: Allows container to control the host Docker daemon
6. **`--pid=host`**: Shares host PID namespace

## Remediation
- Add `USER nonroot` in Dockerfile
- Use Docker secrets or env files for sensitive values
- Remove unnecessary capabilities with `--cap-drop ALL --cap-add` only what's needed
- Never mount `/var/run/docker.sock` unless strictly necessary
- Enable Docker Content Trust