- 필수 기능
- 시작하기
- 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/avoid-add-use-copy
Language: Docker
Severity: Info
Category: Best Practices
This rule encourages the use of COPY
instead of ADD
in Dockerfiles when simply copying files or directories. While both instructions can copy files into the image, ADD
has additional functionality such as extracting local tar archives and fetching remote URLs, which can introduce unexpected behavior.
Using COPY
is preferred because it is more explicit and predictable, reducing the risk of unintended side effects that could occur with ADD
. This leads to clearer, more maintainable Dockerfiles and helps avoid security issues related to downloading remote files during the build process.
See official Docker documentation
FROM python:3.4
ADD requirements.txt /usr/src/app/
FROM python:3.4
COPY requirements.txt /usr/src/app/