busybox:1.38-musl image size, layers and vulnerabilities (2026-11-01)

docker pull busybox:1.38-muslbusybox@sha256:80e38f9a1b39188b8bdb28879178edb322a4402b081a9aedda1924609decd6f6

Size per platform

Compressed download size on Docker Hub for each architecture.

ppc64le1.0 MB
arm/v61.0 MB
riscv641.0 MB
s390x1.0 MB
arm640.9 MB
amd640.9 MB
i3860.9 MB
arm/v70.9 MB

Where the bytes go

Unpacked bytes by directory in the final amd64 filesystem.

/bin1.5 MB
/etc896 B

Layers

The 1 filesystem layers of the amd64 image, in build order, with each layer's compressed size and the build step that made it.

1. BusyBox 1.38.0 (musl), Alpine 3.23.7886 kB

Full build steps

886 kBBusyBox 1.38.0 (musl), Alpine 3.23.7

Known vulnerabilities

0Critical0 with a fix

0High0 with a fix

0Medium0 with a fix

0Low0 with a fix

0Unknown0 with a fix

Trivy found no known vulnerabilities in the 0 packages it identified; this image has no package database for Trivy to read, so a clean result says little.

Packages

No package database found. The image is a static filesystem (for example BusyBox or a single binary), so package-based scanners cannot see inside it.

Image configuration

Base OS: No package manager (scratch/static)
Default user: root (no USER set; the entrypoint may still drop privileges)
Entrypoint: —
Command: sh
Exposed ports: none
Image created: 2026-05-13
amd64 digest: sha256:0bea5460e5899381903a36e09247aa910cbe7df2e3cea9c57a0448ae518700a2

Other BusyBox tags

busybox:1.38-glibc4.7 MB unpacked · 2.2 MB download✓ 0 known busybox:1.38-uclibc1.5 MB unpacked · 0.8 MB download✓ 0 known

busybox:1.38-musl vs busybox:1.38-glibc

Platform sizes and layers: Docker Hub API, checked 2026-11-01. Unpacked size, files and SBOM: measured 2026-10-26 from digest sha256:0bea5460e589. Vulnerabilities: Trivy re-scan 2026-11-01, database 2026-11-01. Methodology.