Avoid commands not made for containers

Docs > Code Analysis > Static Analysis Rules > Avoid commands not made for containers

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/avoid-commands-not-relevant

Language: Docker

Severity: Notice

Category: Best Practices

Description

Some commands do not make sense to use when building a container. They require user inputs which cannot work when building a container. Avoid such commands in a Dockerfile.

Non-Compliant Code Examples

FROM busybox
RUN top
RUN vim

Compliant Code Examples

FROM busybox
RUN mycommand foo bar
RUN apt-get install vim

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