Docker Security Guide

This is your checklist when you need to lock down Docker in production or pass a security audit. It walks you through the full stack: scanning images with Scout and Trivy, dropping capabilities with --cap-drop ALL, running read-only filesystems, applying seccomp and AppArmor profiles, and managing secrets without leaking them in layers or environment variables. You also get network isolation patterns, CIS Docker Benchmark mapping, and recipes for Chainguard's zero-CVE images if you're chasing compliance. Activate it when you're hardening containers, reviewing Dockerfiles for vulnerabilities, or setting up supply chain security with signed images and SBOMs.

skills.sh installs: 619
GitHub stars: 61
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add josiahsiegel/claude-plugin-marketplace --skill docker-security-guide --agent claude-code

Installs into .claude/skills of the current project.

Files

🚨 CRITICAL GUIDELINES

Windows File Path Requirements

MANDATORY: Always Use Backslashes on Windows for File Paths

When using Edit or Write tools on Windows, you MUST use backslashes (\) in file paths, NOT forward slashes (/).

Examples:

❌ WRONG: D:/repos/project/file.tsx
✅ CORRECT: D:\repos\project\file.tsx

This applies to:

Edit tool file_path parameter
Write tool file_path parameter
All file operations on Windows systems

Documentation Guidelines

NEVER create new documentation files unless explicitly requested by the user.

Priority: Update existing README.md files rather than creating new documentation
Repository cleanliness: Keep repository root clean - only README.md unless user requests otherwise
Style: Documentation should be concise, direct, and professional - avoid AI-generated tone
User preference: Only create additional .md files when user specifically asks for documentation