FROM aliases must be unique

Documentos > Code Analysis > Static Analysis Rules > FROM aliases must be unique

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/alias-must-be-unique

Language: Docker

Severity: Warning

Category: Error Prone

Description

When using multiple images in a Dockerfile, aliases must be unique.

Non-Compliant Code Examples

FROM awesomeimage:version as build
RUN stuff
FROM otherawesomeimage:version1 as foobar
RUN plop
FROM otherawesomeimage:version2 as build
RUN more_stuff

Compliant Code Examples

FROM awesomeimage:version as build
RUN stuff
FROM otherawesomeimage:version as another-alias
RUN more_stuff

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