- 필수 기능
- 시작하기
- 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-end-slash
Language: Docker
Severity: Warning
Category: Best Practices
This rule enforces that when the COPY instruction in a Dockerfile has more than two arguments, the last argument must be a directory path ending with a slash (/). This ensures that multiple source files or directories are copied into the specified destination directory correctly. Always ensure that when copying multiple files or directories, the destination path ends with a slash, clearly indicating it is a directory. For example, use COPY package.json yarn.lock my_app/
instead of COPY package.json yarn.lock my_app
. This practice improves clarity and prevents ambiguous or incorrect Docker image builds.
FROM node:carbon
COPY package.json yarn.lock my_app
FROM node:carbon
COPY package.json yarn.lock my_app/