- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- Administrator's Guide
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
",t};e.buildCustomizationMenuUi=t;function n(e){let t='
",t}function s(e){let n=e.filter.currentValue||e.filter.defaultValue,t='${e.filter.label}
`,e.filter.options.forEach(s=>{let o=s.id===n;t+=``}),t+="${e.filter.label}
`,t+=`ID: docker-best-practices/copy-reference-from
Language: Docker
Severity: Warning
Category: Best Practices
This rule enforces that the COPY
instruction must reference a valid build stage alias defined by a preceding FROM
statement using the as
keyword. Specifically, the --from
flag in COPY
should only point to an existing build stage alias, ensuring that the source files are correctly retrieved from the intended build context.
To avoid violations, always declare build stages with FROM <image> as <alias>
before using COPY --from=<alias>
. Verify that the alias used in COPY
matches exactly with the alias declared in the earlier FROM
statement. For example, using FROM debian:jesse as build
followed by COPY --from=build ...
ensures compliance and reliable builds.
FROM debian:jesse as build
COPY --from=build some stuff ./
FROM debian:jesse as build
RUN stuff
FROM debian:jesse
COPY --from=build some stuff ./