Multiple ENTRYPOINT Instructions

MEDIUM

Dockerfile has multiple ENTRYPOINT instructions. Only the last one takes effect, making earlier ones misleading.

Rule Information

Language
Docker
Category
Correctness
Author
Shivasurya
Shivasurya
Last Updated
2026-03-22
Tags
dockerdockerfileentrypointcorrectnessconfigurationmaintainabilityconfusinganti-pattern
CWE References

Interactive Playground

Experiment with the vulnerable code and security rule below. Edit the code to see how the rule detects different vulnerability patterns.

pathfinder scan --ruleset docker/DOCKER-COR-001 --project .
1
2
3
4
5
6
rule.py
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17

About This Rule

Understanding the vulnerability and how it is detected

Detects Dockerfiles with multiple ENTRYPOINT instructions. Docker only honors the last ENTRYPOINT, making earlier ones misleading and potentially causing unexpected runtime behavior. This can lead to confusion and bugs.

How to Fix

Recommended remediation steps

  • 1Review your Dockerfile to address the multiple entrypoint instructions issue
  • 2Follow Docker official best practices for image building
  • 3Use docker build --check to validate Dockerfile syntax and best practices

References

External resources and documentation

Similar Rules

Explore related security rules for Docker

Frequently Asked Questions

Common questions about Multiple ENTRYPOINT Instructions

Dockerfile has multiple ENTRYPOINT instructions. Only the last one takes effect, making earlier ones misleading.
Review the secure code example in the playground above and apply the recommended pattern to your Dockerfile or docker-compose.yml.

New feature

Get these findings posted directly on your GitHub pull requests

The Multiple ENTRYPOINT Instructions rule runs in CI and posts inline review comments on the exact lines — no dashboard, no SARIF viewer.

See how it works