- 필수 기능
- 시작하기
- 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/curl-or-wget
Language: Docker
Severity: Warning
Category: Best Practices
This rule enforces the use of either wget
or curl
exclusively within a Dockerfile, but not both. Mixing these two tools in the same Dockerfile can lead to unnecessary complexity and larger image sizes due to installing multiple similar utilities. It also reduces consistency and maintainability of the Dockerfile.
To comply with this rule, choose either wget
or curl
based on your preference or the base image’s default availability, and use it consistently throughout your Dockerfile. For example, if you decide to use curl
, replace all occurrences of wget
with equivalent curl
commands like curl -O <url>
. This approach ensures clarity and reduces the image footprint.
FROM debian
RUN curl http://bing.com
ADD something somethingelse
RUN wget http://google.com
FROM debian
RUN wget http://google.com
ADD something somethingelse
RUN curl http://bing.com
FROM debian
RUN curl http://google.com
RUN curl http://bing.com