跳到主内容
智客 ZICQ

技能库 智客分类:运维与云 docker-build-strategies

Docker Build Strategies

在写作,审查,或优化多克文件时使用这种技能,即使用户只是说其图像太大,其构造缓慢,或者需要加硬一个容器来制作. 覆盖多相构筑,地层缓存,.dockerignore,非地基用户,并优化图像大小.

2168 安装量

官方网址:skills.sh

技能介绍

先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。

做什么

在写作,审查,或优化多克文件时使用这种技能,即使用户只是说其图像太大,其构造缓慢,或者需要加硬一个容器来制作. 覆盖多相构筑,地层缓存,.dockerignore,非地基用户,并优化图像大小.

何时用

这个技能

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:Docker Build Strategies、Overview、When to use this skill、Do not use this skill when、Core guidance、Multi-stage builds。

文件分析

文件分析:除 SKILL.md 外,正文引用了 references/multi-stage-builds.md、references/layer-caching.md、assets/dockerignore-example、assets/Dockerfile.go、assets/Dockerfile.nodejs、assets/Dockerfile.python,属于带资源的技能包,这些文件按需再读。

官方 description(原文)

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.

Docker Build StrategiesOverviewWhen to use this skillDo not use this skill whenCore guidanceMulti-stage buildsLayer cachingBuild secrets and SSH access.dockerignoreNon-root userImage size optimizationGeneral rules

兼容:Requires Docker 23.0+ (BuildKit default). On Docker 20.10–22.x, set DOCKER_BUILDKIT=1 before building. · 许可:Apache-2.0

来源分类:skills.sh agent-skill

SKILL.md 与 Agent 调用

官方规范 ↗
name
docker-build-strategies
description
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.
compatibility
Requires Docker 23.0+ (BuildKit default). On Docker 20.10–22.x, set DOCKER_BUILDKIT=1 before building.
许可
Apache-2.0
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。
指令中引用的文件 · 7
  • references/multi-stage-builds.md
  • references/layer-caching.md
  • assets/dockerignore-example
  • assets/Dockerfile.go
  • assets/Dockerfile.nodejs
  • assets/Dockerfile.python
  • scripts/verify-build.sh

以下路径提取自原文;文件是否齐全请以来源仓库中的完整目录为准。

具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。

该技能引用了附属文件,请从来源获取完整目录;仅复制 SKILL.md 可能缺少依赖。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。

把 Agent Skill「docker-build-strategies」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-87bdf1c7a3b50570-Docker-%E6%9E%84%E5%BB%BA%E7%AD%96%E7%95%A5.html
请存为 .cursor/skills/docker-build-strategies/SKILL.md 或 .claude/skills/docker-build-strategies/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。
该技能还带 scripts/、references/、assets/ 等文件,请从 https://github.com/docker/skills 取完整目录,不要只建一个 SKILL.md。

GitHub 完整包 ↗

终端安装 · Skills CLI

需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。

npx skills add 'https://github.com/docker/skills' --list

npx skills add 'https://github.com/docker/skills' --skill 'docker-build-strategies'

CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。

阅读排版
--- name: docker-build-strategies description: 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. license: Apache-2.0 compatibility: Requires Docker 23.0+ (BuildKit default). On Docker 20.10–22.x, set DOCKER_BUILDKIT=1 before building. --- # 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 `.dockerignore` file 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. 1. Name every stage explicitly (`FROM ... AS build`, `FROM ... AS runtime`). 2. Use the smallest appropriate base for the runtime stage: `distroless`, `alpine`, or `slim` variants. 3. Copy only the final artifact into the runtime stage with `COPY --from=build`. 4. Use `COPY --link` when 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. 1. 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 of `COPY`-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, `COPY` it instead. 2. 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 ...` — no `rm -rf /var/lib/apt/lists/*` needed, since the cache lives outside the image layer. `sharing=locked` is required because apt needs exclusive access to its cache directories. - apk (Alpine — per the Alpine wiki, not a Docker-verified doc; `references/layer-caching.md` links the source): `RUN --mount=type=cache,target=/etc/apk/cache,sharing=locked apk add ...` — drop `--no-cache` so downloaded packages land in the mounted cache directory instead of being discarded. 3. Pin base image tags to a specific version or digest — never use `latest` in production. 4. Combine related `RUN` commands 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. 1. **Do NOT** pass credentials through `ARG` or `ENV`. Both end up in the image layers and are inspectable via `docker history`. 2. **Do NOT** `COPY` credential files into the build context: `.npmrc`, `.pypirc`, `.netrc`, `pip.conf`, Maven `settings.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. 3. **Do NOT** echo, write, or expand the secret value inside a `RUN` command in a way that persists it to a layer or emits it to build logs. Access the secret file (e.g., `/run/secrets/`, or directly via the mount `target=`) — never `echo "$(cat /run/secrets/X)"`, never substitute it into a shell argument that will be logged with `--progress=plain`. 4. **Use `RUN --mount=type=secret`** for package manager registry credentials: ```dockerfile RUN --mount=type=secret,id=npmrc,target=/root/.npmrc,required=false \ --mount=type=cache,target=/root/.npm \ npm ci --omit=dev ``` The secret is available only inside that `RUN`, never written to a layer. Use `required=true` when 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); use `required=false` only when the secret is optional (the build can succeed with public packages alone). 5. **Use `RUN --mount=type=ssh`** for fetching private Git repositories or modules. The build container has no `known_hosts` by default — populate it inside the same `RUN`: ```dockerfile RUN --mount=type=ssh \ mkdir -p -m 0700 /root/.ssh && \ ssh-keyscan github.com >> /root/.ssh/known_hosts && \ git clone [email protected]:org/private-repo.git ``` Do NOT use `StrictHostKeyChecking=no` as a shortcut — it disables host-key verification entirely. `ssh-keyscan` accepts 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 into `known_hosts` instead of scanning. 6. **Invoke buildx with the secret and SSH sources:** ```bash # --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 \ . ``` The `RUN --mount=type=ssh` step can use every key that `ssh-add -l` lists, so expose only the key this build needs. In an interactive terminal, run `ssh-agent bash` to start a shell with a dedicated agent, then run `ssh-add `, confirm that `ssh-add -l` lists 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=`; BuildKit rejects passphrase-protected keys in this form, so load those into an agent instead. 7. `.dockerignore` exclusions of `.env` and 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 - `.env` files 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. 1. Create a dedicated user and group in the runtime stage: ```dockerfile RUN addgroup --system --gid 1001 appgroup && \ adduser --system --uid 1001 --ingroup appgroup appuser ``` 2. Set ownership on application files: `COPY --from=build --chown=appuser:appgroup /app /app` 3. 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 1001` above), not named users. `--link` creates an independent layer where named users from prior `RUN` instructions are not available. 4. Place the `USER appuser` instruction after all file operations and before `ENTRYPOINT`/`CMD`. 5. On distroless images, use the built-in nonroot user: `USER nonroot:nonroot`. ### Image size optimization 1. Prefer `FROM scratch` (Go static binaries), distroless, or Alpine-based images for the runtime stage. 2. 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. 3. Do not install documentation, man pages, or debug tools in the runtime image. 4. Use `.dockerignore` aggressively to minimize the build context. ### General rules - Always include a `# syntax=docker/dockerfile:1` directive as the first line to enable BuildKit features. - Set `WORKDIR` before any `COPY` or `RUN` instructions — never rely on the default `/`. - Prefer `ENTRYPOINT` with exec form (`["binary"]`) over shell form. - Add `EXPOSE` to 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, use `docker-destructive-guardrails`. ## References - `references/multi-stage-builds.md` — Language-specific multi-stage patterns for Go, Node.js, Python, and Java - `references/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 user - `assets/Dockerfile.nodejs` — Multi-stage Node.js build with proper layer caching and non-root user - `assets/Dockerfile.python` — Python build with virtual env, layer ordering, and non-root user - `assets/dockerignore-example` — Comprehensive `.dockerignore` template ## 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 the `Dockerfile`), with the script path resolved under this skill's directory: ```bash bash "/scripts/verify-build.sh" [--help] [IMAGE_NAME] ``` Replace `` with the absolute path of the folder that contains this `SKILL.md`; the `scripts/` 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, run `docker build -t verify-build-test .`, then `docker images verify-build-test` and `docker inspect verify-build-test --format '{{.Config.User}}'`. Exit status is `0` when all Docker commands succeed or help is requested, the failing Docker command's non-zero status when verification fails, and `2` for invalid arguments. ## Checks - `checks/verification.md` — Detailed verification runbook for manual review.

相关技能

运维与云

Docker Essentials

用于容器管理,图像操作,调试的基本道克命令和工作流程.

运维与云

Find Skills

从开放的代理技能生态系统中发现并安装技能. 使用时:(1)用户问"我如何做X",X可能拥有现有技能,(2)用户说"为X找到技能"或"是否为X有技能",(3)用户问"你能否做X",X是专门能力,(4)用户想扩展代理能力,(5)用户想搜索工具,模板,或工作流程,(6)用户提到他们希望…

运维与云

Microsoft Foundry

构建,部署,评价,优化,微调,管理微软创始代理,模型,资源最终结束. 用法:铸造、azd ai代理、azd 提供/部署、托管代理脚手架/开发/运行/部署/拖放、即时代理创建、创建代理、更新代理、添加代理工具、援引代理、代理.yaml、评估代理、批量活化、连续活化、持续监测、代理C…

运维与云

Azure Deploy

执行已有.azure/部署计划.md和基础设施文件的ALREADY-PREPARED应用程序的Azure部署。 当用户向 CREATE 请求新应用程序时, 请不要使用此技能 。 这种技能运行了 azd上行, azd 部署, trarraform 应用, 和 az 部署命令带有内置…