multi-stage-dockerfile

github/awesome-copilot/multi-stage-dockerfile

此技能旨在帮助您创建高效的多阶段 Dockerfile，遵循最佳实践，从而生成更小、更安全的容器镜像。它涵盖了多阶段结构、基础镜像选择、层优化、安全实践和性能考虑等方面。多阶段构建使用构建阶段进行编译、依赖安装等构建时操作，并使用单独的运行时阶段仅包含运行应用所需的内容。通过仅复制必要的构建产物，可以显著减小最终镜像的大小。此外，该技能强调使用官方最小基础镜像、精确版本标签、非 root 用户运行、移除不必要的包以及利用构建缓存等策略，以确保构建的可重复性、安全性和效率。

安装量 · 286查看来源

Installation

npx skills add https://github.com/github/awesome-copilot --skill multi-stage-dockerfile

技能文件

SKILL.md

最近同步 · 2026年9月30日

SKILL.md›

---
name: multi-stage-dockerfile
description: 'Create optimized multi-stage Dockerfiles for any language or framework'
---

Your goal is to help me create efficient multi-stage Dockerfiles that follow best practices, resulting in smaller, more secure container images.

## Multi-Stage Structure

- Use a builder stage for compilation, dependency installation, and other build-time operations
- Use a separate runtime stage that only includes what's needed to run the application
- Copy only the necessary artifacts from the builder stage to the runtime stage
- Use meaningful stage names with the `AS` keyword (e.g., `FROM node:18 AS builder`)
- Place stages in logical order: dependencies → build → test → runtime

## Base Images

- Start with official, minimal base images when possible
- Specify exact version tags to ensure reproducible builds (e.g., `python:3.11-slim` not just `python`)
- Consider distroless images for runtime stages where appropriate
- Use Alpine-based images for smaller footprints when compatible with your application
- Ensure the runtime image has the minimal necessary dependencies

## Layer Optimization

- Organize commands to maximize layer caching
- Place commands that change frequently (like code changes) after commands that change less frequently (like dependency installation)
- Use `.dockerignore` to prevent unnecessary files from being included in the build context
- Combine related RUN commands with `&&` to reduce layer count
- Consider using COPY --chown to set permissions in one step

## Security Practices

- Avoid running containers as root - use `USER` instruction to specify a non-root user
- Remove build tools and unnecessary packages from the final image
- Scan the final image for vulnerabilities
- Set restrictive file permissions
- Use multi-stage builds to avoid including build secrets in the final image

## Performance Considerations

- Use build arguments for configuration that might change between environments
- Leverage build cache efficiently by ordering layers from least to most frequently changing
- Consider parallelization in build steps when possible
- Set appropriate environment variables like NODE_ENV=production to optimize runtime behavior
- Use appropriate healthchecks for the application type with the HEALTHCHECK instruction