Do not use multiple ENTRYPOINT

Docs > Code Analysis > Static Analysis Rules > Do not use multiple ENTRYPOINT

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/multiple-entrypoint

Language: Docker

Severity: Notice

Category: Best Practices

Description

Do not use multiple ENTRYPOINT instructions, only the last one is used.

Non-Compliant Code Examples

FROM awesomeimage
ENTRYPOINT /foo/bar
ENTRYPOINT /foo/baz

Compliant Code Examples

FROM awesomeimage
ENTRYPOINT /foo/bar

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