github-starred/awesome-compose
2
0
Fork 0
mirror of https://github.com/docker/awesome-compose.git synced 2026-07-17 05:33:32 -05:00
Code Issues 9.3k Packages Projects Releases Wiki Activity

[GH-ISSUE #753] Optimization: Slice away layer build-time bloat by cleaning package caches in Dockerfiles #17594

New Issue
Closed
opened 2026-07-12 18:51:13 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-07-12 18:51:13 -05:00
Owner
Copy Link

Originally created by @BiosSystem on GitHub (May 30, 2026).
Original GitHub issue: https://github.com/docker/awesome-compose/issues/753

Problem Description

Several example Dockerfiles install packages using standard package managers (like apt or apk) but do not clean up the package manager cache and list files afterwards. This leaves unnecessary temporary files in the image layers, leading to container image bloat and slow pull/deployment times. Hadolint and Docker optimization guides recommend cleaning up lists and caches in the same RUN command where installation occurs.

Affected Examples

  1. spring-postgres (spring-postgres/backend/Dockerfile)
    • At line 14: Runs apt-get install -y --no-install-recommends git but does not clean up the /var/lib/apt/lists/* cache directory.
  2. wasmedge-kafka-mysql (wasmedge-kafka-mysql/etl/Dockerfile)
    • At line 5: Runs apt-get update && apt-get install -y git clang without cleaning up the apt lists.
  3. wasmedge-mysql-nginx (wasmedge-mysql-nginx/backend/Dockerfile)
    • Runs apt-get install without directory cleanup.

Proposed Remediations

Add cache and lists cleanup to the package installation commands:
For apt-get based images:

RUN apt-get update && apt-get install -y --no-install-recommends \
    git \
    clang \
    && rm -rf /var/lib/apt/lists/*

For apk based images, use --no-cache:

RUN apk add --no-cache git
Originally created by @BiosSystem on GitHub (May 30, 2026). Original GitHub issue: https://github.com/docker/awesome-compose/issues/753 ### Problem Description Several example Dockerfiles install packages using standard package managers (like `apt` or `apk`) but do not clean up the package manager cache and list files afterwards. This leaves unnecessary temporary files in the image layers, leading to container image bloat and slow pull/deployment times. Hadolint and Docker optimization guides recommend cleaning up lists and caches in the same `RUN` command where installation occurs. ### Affected Examples 1. **`spring-postgres`** (`spring-postgres/backend/Dockerfile`) - At line 14: Runs `apt-get install -y --no-install-recommends git` but does not clean up the `/var/lib/apt/lists/*` cache directory. 2. **`wasmedge-kafka-mysql`** (`wasmedge-kafka-mysql/etl/Dockerfile`) - At line 5: Runs `apt-get update && apt-get install -y git clang` without cleaning up the apt lists. 3. **`wasmedge-mysql-nginx`** (`wasmedge-mysql-nginx/backend/Dockerfile`) - Runs `apt-get install` without directory cleanup. ### Proposed Remediations Add cache and lists cleanup to the package installation commands: For `apt-get` based images: ```dockerfile RUN apt-get update && apt-get install -y --no-install-recommends \ git \ clang \ && rm -rf /var/lib/apt/lists/* ``` For `apk` based images, use `--no-cache`: ```dockerfile RUN apk add --no-cache git ```
GiteaMirror commented 2026-07-12 18:51:13 -05:00
Author
Owner
Copy Link

@BiosSystem commented on GitHub (May 30, 2026):

Closing as this issue targets example files.

<!-- gh-comment-id:4582562241 --> @BiosSystem commented on GitHub (May 30, 2026): Closing as this issue targets example files.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
good first issue
proposal
pull-request
Mirrored from GitHub Pull Request
 question
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/awesome-compose#17594
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?