Missing dnf clean all

LOW

RUN uses 'dnf install' without 'dnf clean all'. This increases image size.

Rule Information

Language
Docker
Category
Best Practice
Author
Shivasurya
Shivasurya
Last Updated
2026-03-22
Tags
dockerdockerfilednfpackage-managerfedorarhelcachecleanupimage-sizeoptimizationbest-practice
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-BP-013 --project .
1
2
3
4
rule.py
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19

About This Rule

Understanding the vulnerability and how it is detected

Detects 'dnf install' commands without subsequent 'dnf clean all'. Package manager caches unnecessarily increase image size by storing package metadata and repository information that is not needed at runtime.

How to Fix

Recommended remediation steps

  • 1Review your Dockerfile to address the missing dnf clean all 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 Missing dnf clean all

RUN uses 'dnf install' without 'dnf clean all'. This increases image size.
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 Missing dnf clean all rule runs in CI and posts inline review comments on the exact lines — no dashboard, no SARIF viewer.

See how it works