Use absolute workdir

Documentos > Code Analysis > Static Analysis Rules > Use absolute workdir

This page is not yet available in Spanish. We are working on its translation.
If you have any questions or feedback about our current translation project, feel free to reach out to us!

Metadata

ID: docker-best-practices/absolute-workdir

Language: Docker

Severity: Warning

Category: Best Practices

Description

When using a relative WORKDIR, you may run into problems since you are dependent on previous WORKDIR instructions. Using an absolute WORKDIR ensures you have the right path no matter where the instruction is positioned.

Non-Compliant Code Examples

FROM busybox
WORKDIR usr/src/app

Compliant Code Examples

FROM busybox
WORKDIR /usr/src/app

WORKDIR $MYWORKDIR

How to use this rule

1
2
rulesets:
  - docker-best-practices     # Rules to enforce Docker best practices.

Create a static-analysis.datadog.yml with the content above at the root of your repository
Use our free IDE Plugins or add Code Analysis scans to your CI pipelines
Get feedback on your code

For more information, please read the Code Analysis documentation

VS Code Extension

Identify code vulnerabilities directly in your
VS Code editor

JetBrains Plugin

Identify code vulnerabilities directly in
JetBrains products