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

docker pull busybox:1.38-glibcbusybox@sha256:99813cb178ace2cd9c6c53ee3bddef5d2f5708aa438335111d7a9e3c5e1aaebe

Size per platform

Compressed download size on Docker Hub for each architecture.

ppc64le2.5 MB
i3862.3 MB
amd642.2 MB
s390x2.1 MB
riscv642.0 MB
arm641.9 MB
arm/v51.8 MB
arm/v71.6 MB

Where the bytes go

Unpacked bytes by directory in the final amd64 filesystem.

/lib3.4 MB
/bin1.1 MB
/etc1 kB

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 (glibc), Debian 132.2 MB

Full build steps

2.2 MBBusyBox 1.38.0 (glibc), Debian 13

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:f97baa533a26513c453a362be331a43eb60214302f449c16571b23cea141dce4

Other BusyBox tags

busybox:1.38-musl1.8 MB unpacked · 0.9 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:f97baa533a26. Vulnerabilities: Trivy re-scan 2026-11-01, database 2026-11-01. Methodology.