DockerState

Home › Base OS images › busybox › 1.38-uclibc

busybox:1.38-uclibc

BusyBox utilities on an empty root, in three libc flavours, tag 1.38-uclibc, built on No package manager (scratch/static). Pushed to Docker Hub 2 days ago.

✓ 0 known Starts as root6 platforms

0.8 MBdownload (compressed)
1.5 MBunpacked on disk
1filesystem layers
0packages
6files
docker pull busybox:1.38-uclibcbusybox@sha256:b2e35951f72501f6a99f1bf45bcfe6d4795be08c518c2f97d0ed2fe776958a3b

Size per platform

Compressed download size on Docker Hub for each architecture.

  • riscv640.9 MB
  • arm640.8 MB
  • amd640.8 MB
  • arm/v50.8 MB
  • i3860.7 MB
  • arm/v70.7 MB

Where the bytes go

Unpacked bytes by directory in the final amd64 filesystem.

  • /bin1.3 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.

Full build steps
  1. 775 kBBusyBox 1.38.0 (uclibc), Buildroot 2026.08.1, 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:d474170a9f5c5fcca53f8187d65e59ab58b22092602068531645164b61e5ff6e

Other BusyBox tags

busybox:1.38-musl1.8 MB unpacked · 0.9 MB download✓ 0 known busybox:1.38-glibc4.7 MB unpacked · 2.2 MB download✓ 0 known

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