docker-build-strategies
Skill1 starsChanged 15 days agoMITView on GitHub
Use this skill when writing, reviewing, or optimizing Dockerfiles, even if the user just says their image is too large, their build is slow, or they need to harden a container for production. Covers multi-stage builds, layer caching, .dockerignore, non-root users, and image size optimization.
- Reads credentials
- Deletes or force-pushes
- Installs packages
1 other project uses a version of this.
Adopted by
Most recently taken up by
- docker/skillsword for word, first seen Nov 13, 2026
Other versions1 project uses a version of this.
Word for word · 1
- docker/skills★ 635100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository58 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .agents/skills/vercel-composition-patterns/AGENTS.mdAGENTS.md
- .agents/skills/vercel-react-best-practices/AGENTS.mdAGENTS.md
- .claude/skills/vercel-composition-patterns/AGENTS.mdAGENTS.md
- .claude/skills/vercel-react-best-practices/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- ai-in-the-productSkill
- backend-apiSkill
- database-quickSkill
- data-ml-quickstartSkill
- debug-fastSkill
- demo-and-pitchSkill
- deploy-fastSkill
- deploy-to-vercelSkill
- docker-compose-patternsSkill
- docker-destructive-guardrailsSkill
- docker-project-foundationsSkill
- find-skillsSkill
- frontend-nextjs-vercelSkill
- git-githubSkill
- kickoffSkill
- pitch-deckSkill
- rapid-prototypeSkill
- repo-polishSkill
- security-basicsSkill
- smoke-testingSkill
- team-syncSkill
- ui-polishSkill
- vercel-composition-patternsSkill
- vercel-react-best-practicesSkill
- verification-before-doneSkill
- ai-in-the-productSkill
- backend-apiSkill
- database-quickSkill
- data-ml-quickstartSkill
- debug-fastSkill
- demo-and-pitchSkill
- deploy-fastSkill
- deploy-to-vercelSkill
- docker-build-strategiesSkill
- docker-compose-patternsSkill
- docker-destructive-guardrailsSkill
- docker-project-foundationsSkill
- find-skillsSkill
- frontend-nextjs-vercelSkill
- git-githubSkill
- kickoffSkill
- pitch-deckSkill
- rapid-prototypeSkill
- repo-polishSkill
- security-basicsSkill
- smoke-testingSkill
- team-syncSkill
- ui-polishSkill
- vercel-composition-patternsSkill
- vercel-react-best-practicesSkill
- verification-before-doneSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
18 rules. About 0 are common, 6 are distinctive, and 12 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
12
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 25
Do not use this skill when:
- Distinctive: line 35
Use multi-stage builds when the project has a build step or when build-time dependencies differ from runtime.
- Very specific: line 38
Use the smallest appropriate base for the runtime stage: distroless, alpine, or slim variants.
- Very specific: line 40
Use COPY --link when copying from a prior stage or adding static files — it improves cache reuse by making the COPY independent of previous …
- Distinctive: line 49
Use BuildKit cache mounts for package manager caches:
- Very specific: line 62
Never bake credentials into the image.
- Very specific: line 99
Always generate a .dockerignore alongside the Dockerfile.
- Distinctive: line 111
Always configure the final image to run as a non-root user.
- Distinctive: line 113
Create a dedicated user and group in the runtime stage:
- Very specific: line 119
When combining --chown with COPY --link, always use the numeric UID:GID you assigned (e.g., --chown=1001:1001 if you used --uid 1001 --gid …
- Very specific: line 120
Place the USER appuser instruction after all file operations and before ENTRYPOINT/CMD.
- Very specific: line 125
Prefer FROM scratch (Go static binaries), distroless, or Alpine-based images for the runtime stage.
- Distinctive: line 127
Do not install documentation, man pages, or debug tools in the runtime image.
- Very specific: line 128
Use .dockerignore aggressively to minimize the build context.
- Very specific: line 132
Always include a # syntax=docker/dockerfile:1 directive as the first line to enable BuildKit features.
- Very specific: line 134
Prefer ENTRYPOINT with exec form (["binary"]) over shell form.
- Very specific: line 135
Add EXPOSE to document the listening port.
- Very specific: line 136
Add metadata labels: LABEL org.opencontainers.image.source=...
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Docker Build Strategies
Overview
This skill provides rules and patterns for writing and reviewing production-quality Dockerfiles. Apply it when the main task is image-build quality: multi-stage builds, cache behavior, non-root execution, build context hygiene, and runtime image size.
When to use this skill
Activate this skill when:
- Creating a new Dockerfile for any language or framework
- Optimizing an existing Dockerfile for size, speed, or security
- Reviewing a Dockerfile for best-practice compliance
- Adding a
.dockerignorefile to a project
Do not use this skill when
Do not use this skill when:
- The project has no Docker setup yet and the main need is a first-pass scaffold
- The main task is wiring services together in
compose.yaml - The main task is debugging Compose startup ordering, networking, or development overrides
Core guidance
Multi-stage builds
Use multi-stage builds when the project has a build step or when build-time dependencies differ from runtime. Separate build-time dependencies from the runtime image.
- Name every stage explicitly (
FROM ... AS build,FROM ... AS runtime). - Use the smallest appropriate base for the runtime stage:
distroless,alpine, orslimvariants. - Copy only the final artifact into the runtime stage with
COPY --from=build. - Use
COPY --linkwhen copying from a prior stage or adding static files — it improves cache reuse by making the COPY independent of previous layers.
See references/multi-stage-builds.md for language-specific patterns (Go, Node, Python, Java).
Layer caching
Order Dockerfile instructions from least-frequently-changed to most-frequently-changed.
- Place dependency manifests (
package.json,go.mod,requirements.txt) and install steps before copying application source code. Bind-mount the manifest into the install step instead ofCOPY-ing it, so it never enters a layer:RUN --mount=type=bind,source=package.json,target=package.json --mount=type=bind,source=package-lock.json,target=package-lock.json npm ci. This is safe for install commands that only read the manifest (npm ci,pip install -r,go mod download); if a step also needs to write the manifest back into the image,COPYit instead. - Use BuildKit cache mounts for package manager caches:
- Go:
RUN --mount=type=cache,target=/go/pkg/mod go build ... - Node:
RUN --mount=type=cache,target=/root/.npm npm ci - Python:
RUN --mount=type=cache,target=/root/.cache/pip pip install ... - apt:
RUN --mount=type=cache,target=/var/cache/apt,sharing=locked --mount=type=cache,target=/var/lib/apt,sharing=locked apt-get update && apt-get install -y ...— norm -rf /var/lib/apt/lists/*needed, since the cache lives outside the image layer.sharing=lockedis required because apt needs exclusive access to its cache directories. - apk (Alpine — per the Alpine wiki, not a Docker-verified doc;
references/layer-caching.mdlinks the source):RUN --mount=type=cache,target=/etc/apk/cache,sharing=locked apk add ...— drop--no-cacheso downloaded packages land in the mounted cache directory instead of being discarded.
- Go:
- Pin base image tags to a specific version or digest — never use
latestin production. - Combine related
RUNcommands with&&to reduce layer count, but keep logically distinct steps separate for cache granularity.
See references/layer-caching.md for detailed cache invalidation rules and cache mount patterns.
Build secrets and SSH access
Never bake credentials into the image. Use BuildKit secrets and SSH mounts so credentials are available only during the specific RUN step that needs them, and never persist in any layer or docker history output.
- Do NOT pass credentials through
ARGorENV. Both end up in the image layers and are inspectable viadocker history. - Do NOT
COPYcredential files into the build context:.npmrc,.pypirc,.netrc,pip.conf, Mavensettings.xml,.env, cloud credentials (~/.aws/credentials,~/.config/gcloud/, service-account JSON files,~/.azure/), secret-manager tokens (~/.vault-token), package-registry tokens (~/.cargo/credentials.toml), TLS keys (*.pem,*.p12),kubeconfig, SSH keys (id_rsa,id_dsa,id_ed25519,id_ecdsa). Even when the final stage does not copy them forward, they live in intermediate layers and the build cache. - Do NOT echo, write, or expand the secret value inside a
RUNcommand in a way that persists it to a layer or emits it to build logs. Access the secret file (e.g.,/run/secrets/<id>, or directly via the mounttarget=) — neverecho "$(cat /run/secrets/X)", never substitute it into a shell argument that will be logged with--progress=plain. - Use
RUN --mount=type=secretfor package manager registry credentials:
The secret is available only inside thatRUN --mount=type=secret,id=npmrc,target=/root/.npmrc,required=false \ --mount=type=cache,target=/root/.npm \ npm ci --omit=devRUN, never written to a layer. Userequired=truewhen the build will always need the credential (e.g., all packages come from a private registry, so missing the secret should fail the build immediately); userequired=falseonly when the secret is optional (the build can succeed with public packages alone). - Use
RUN --mount=type=sshfor fetching private Git repositories or modules. The build container has noknown_hostsby default — populate it inside the sameRUN:
Do NOT useRUN --mount=type=ssh \ mkdir -p -m 0700 /root/.ssh && \ ssh-keyscan github.com >> /root/.ssh/known_hosts && \ git clone git@github.com:org/private-repo.gitStrictHostKeyChecking=noas a shortcut — it disables host-key verification entirely.ssh-keyscanaccepts whatever host key the server presents each time the step runs; nothing is pinned between builds. For stronger assurance, compare it against the provider's published host key fingerprints, or write the published key intoknown_hostsinstead of scanning. - Invoke buildx with the secret and SSH sources:
The# --ssh default forwards this shell's SSH agent (SSH_AUTH_SOCK); list every key the build can use: ssh-add -l docker buildx build \ --secret id=npmrc,src=$HOME/.npmrc \ --ssh default \ .RUN --mount=type=sshstep can use every key thatssh-add -llists, so expose only the key this build needs. In an interactive terminal, runssh-agent bashto start a shell with a dedicated agent, then runssh-add <key-file>, confirm thatssh-add -llists only that key, and run the build in that shell. A tool that starts a new shell for each command loses that agent between commands, so ask the user to run these steps. Alternatively, pass an unencrypted key file, such as a dedicated deploy key, directly with--ssh default=<key-file>; BuildKit rejects passphrase-protected keys in this form, so load those into an agent instead. .dockerignoreexclusions of.envand credential files are defense in depth, not the primary mechanism — keep them, but do not rely on them as your only protection.
See references/multi-stage-builds.md for per-language patterns (npm, pip, Maven, Go GOPRIVATE).
.dockerignore
Always generate a .dockerignore alongside the Dockerfile. Exclude:
.git/,.github/,.vscode/,.idea/node_modules/,__pycache__/,.venv/,vendor/(when rebuilt in the build stage)*.md,LICENSE,docs/- Build outputs, test artifacts, and IDE configs
.envfiles and any secrets
See assets/dockerignore-example for a comprehensive template.
Non-root user
Always configure the final image to run as a non-root user.
- Create a dedicated user and group in the runtime stage:
RUN addgroup --system --gid 1001 appgroup && \ adduser --system --uid 1001 --ingroup appgroup appuser - Set ownership on application files:
COPY --from=build --chown=appuser:appgroup /app /app - When combining
--chownwithCOPY --link, always use the numeric UID:GID you assigned (e.g.,--chown=1001:1001if you used--uid 1001 --gid 1001above), not named users.--linkcreates an independent layer where named users from priorRUNinstructions are not available. - Place the
USER appuserinstruction after all file operations and beforeENTRYPOINT/CMD. - On distroless images, use the built-in nonroot user:
USER nonroot:nonroot.
Image size optimization
- Prefer
FROM scratch(Go static binaries), distroless, or Alpine-based images for the runtime stage. - Install OS packages with a BuildKit cache mount rather than
rm -rf-ing the cache in the same layer — see "Layer caching" above. The cache mount keeps the package cache out of the image layer entirely, so no cleanup step is needed. - Do not install documentation, man pages, or debug tools in the runtime image.
- Use
.dockerignoreaggressively to minimize the build context.
General rules
- Always include a
# syntax=docker/dockerfile:1directive as the first line to enable BuildKit features. - Set
WORKDIRbefore anyCOPYorRUNinstructions — never rely on the default/. - Prefer
ENTRYPOINTwith exec form (["binary"]) over shell form. - Add
EXPOSEto document the listening port. - Add metadata labels:
LABEL org.opencontainers.image.source=...
Related skills
- For first-time Docker project scaffolding and deciding which files to create, use
docker-project-foundations. - For service dependencies, health checks, overrides, networks, and volume patterns, use
docker-compose-patterns. - For destructive Docker CLI commands (
docker system prune,docker rm -f, image/network/builder pruning) and a cross-product index of destructive-command guardrails, usedocker-destructive-guardrails.
References
references/multi-stage-builds.md— Language-specific multi-stage patterns for Go, Node.js, Python, and Javareferences/layer-caching.md— Deep dive on layer ordering, cache invalidation, and BuildKit cache mounts
Assets
assets/Dockerfile.go— Multi-stage Go build with distroless runtime and non-root userassets/Dockerfile.nodejs— Multi-stage Node.js build with proper layer caching and non-root userassets/Dockerfile.python— Python build with virtual env, layer ordering, and non-root userassets/dockerignore-example— Comprehensive.dockerignoretemplate
Scripts
scripts/verify-build.sh— Builds the Dockerfile in the current directory, then reports image size and configured user. Run it from the project root (the directory that contains theDockerfile), with the script path resolved under this skill's directory:
Replacebash "<skill-dir>/scripts/verify-build.sh" [--help] [IMAGE_NAME]<skill-dir>with the absolute path of the folder that contains thisSKILL.md; thescripts/path is relative to that folder, not to the project. Do not change into the skill directory first: the script builds whatever is in the current directory. If the skill directory cannot be resolved, rundocker build -t verify-build-test ., thendocker images verify-build-testanddocker inspect verify-build-test --format '{{.Config.User}}'. Exit status is0when all Docker commands succeed or help is requested, the failing Docker command's non-zero status when verification fails, and2for invalid arguments.
Checks
checks/verification.md— Detailed verification runbook for manual review.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

