multi-stage-dockerfile

작성자: github

모든 언어나 프레임워크에 최적화되고 안전한 멀티 스테이지 Dockerfile을 빌드합니다. 빌더와 런타임 스테이지를 분리하여 구조화하고, 필요한 아티팩트만 복사하여 최종 이미지 크기와 공격 표면을 최소화합니다. 명령어를 변경 빈도가 낮은 순서에서 높은 순서로 정렬하고, .dockerignore와 명령어 통합을 결합하여 레이어 캐싱 최적화를 강조합니다. Alpine, distroless 또는 공식 slim 변형과 같은 최소 기본 이미지를 정확한 버전 고정과 함께 권장합니다...

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

ZIP 다운로드 GitHub

35.8k

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