How do I install the Containerization skill?

Run npx skillmds@latest add bmaltais/containerization in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Containerization safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Containerization?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Containerization free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Containerization?

bmaltais (@bmaltais) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Containerization by bmaltais — Agent Skill

Name: Containerization
Author: bmaltais

Containerization

Comprehensive best practices for creating optimized, secure, and efficient Docker images and managing containers. Covers multi-stage builds, image layer optimization, security scanning, and runtime best practices. Use when reviewing or writing Dockerfiles, docker-compose files, or container deployment configs. Trigger on phrases like "review my Dockerfile", "optimize this image", "Docker best practices", "container security", "multi-stage build", "reduce image size", "docker-compose review".

bmaltais e9a7fdf 5 files · 15.6 KB Updated Sep 17, 2026

File contents

Containerization & Docker Best Practices

Guide developers in building efficient, secure, and maintainable Docker images.

Core Principles

Immutability — Never modify running containers; build new images for every change.
Portability — Externalize config; images run identically across environments.
Isolation — One process per container; use namespaces and resource limits.
Efficiency — Smaller images = faster builds, pulls, deploys, fewer CVEs.

Routing Table

Topic	Reference
Dockerfile authoring (multi-stage, layers, COPY, CMD, ENV)	`references/dockerfile.md`
Security (non-root, minimal base, signing, secrets, caps)	`references/security.md`
Runtime & orchestration (resources, logging, volumes, nets)	`references/runtime.md`
Review checklist & troubleshooting	`references/checklist.md`

Quick Decision Guide

Compiled language? → Multi-stage build mandatory. See references/dockerfile.md.
Security review? → Start with references/security.md + references/checklist.md.
Image too large? → Check base image, layer optimization, .dockerignore in references/dockerfile.md.
Runtime issues? → Resource limits, health checks, logging in references/runtime.md.

Key Rules (Always Apply)

Use specific version tags, never latest in production.
Run as non-root user — create a dedicated user in every Dockerfile.
Use exec form for CMD/ENTRYPOINT (["cmd", "arg"] not shell form).
Never embed secrets in image layers.
Always include a HEALTHCHECK instruction.
Always include a comprehensive .dockerignore file.

---name: containerizationdescription: Comprehensive best practices for creating optimized, secure, and efficient Docker images and managing containers. Covers multi-stage builds, image layer optimization, security scanning, and runtime best practices. Use when reviewing or writing Dockerfiles, docker-compose files, or container deployment configs. Trigger on phrases like "review my Dockerfile", "optimize this image", "Docker best practices", "container security", "multi-stage build", "reduce image size", "docker-compose review".---# Containerization & Docker Best PracticesGuide developers in building efficient, secure, and maintainable Docker images.## Core Principles1. **Immutability** — Never modify running containers; build new images for every change.2. **Portability** — Externalize config; images run identically across environments.3. **Isolation** — One process per container; use namespaces and resource limits.4. **Efficiency** — Smaller images = faster builds, pulls, deploys, fewer CVEs.## Routing Table| Topic | Reference || ---------------------------------------------- | -------------------------- || Dockerfile authoring (multi-stage, layers, COPY, CMD, ENV) | `references/dockerfile.md` || Security (non-root, minimal base, signing, secrets, caps) | `references/security.md` || Runtime & orchestration (resources, logging, volumes, nets) | `references/runtime.md` || Review checklist & troubleshooting | `references/checklist.md` |## Quick Decision Guide- **Compiled language?** → Multi-stage build mandatory. See `references/dockerfile.md`.- **Security review?** → Start with `references/security.md` + `references/checklist.md`.- **Image too large?** → Check base image, layer optimization, `.dockerignore` in `references/dockerfile.md`.- **Runtime issues?** → Resource limits, health checks, logging in `references/runtime.md`.## Key Rules (Always Apply)- Use **specific version tags**, never `latest` in production.- Run as **non-root user** — create a dedicated user in every Dockerfile.- Use **exec form** for CMD/ENTRYPOINT (`["cmd", "arg"]` not shell form).- **Never** embed secrets in image layers.- Always include a **HEALTHCHECK** instruction.- Always include a comprehensive **`.dockerignore`** file.

Frequently asked questions