Alpine — Minimalism as a Design Goal

Chapter 1's own compare-table already flagged Alpine as the one family in this course not using systemd. This chapter explains why — Alpine isn't Debian/Fedora/Arch with some things removed; nearly every major component is deliberately swapped for a smaller alternative, minimalism chosen as a first-class goal rather than an afterthought.

musl vs. glibc — A Different C Standard Library Entirely

Every other family in this course — Debian, Ubuntu, Fedora, RHEL, Arch — uses glibc (the GNU C Library), the long-standing, feature-complete standard most software is built and tested against. Alpine uses musl instead — a much smaller, simpler, more strictly standards-compliant C library.

BusyBox — Dozens of Utilities, One Small Binary

Instead of the full GNU coreutils most distros ship, Alpine uses BusyBox — a single, compact executable providing simplified implementations of dozens of standard Unix utilities (ls, grep, sed, mount, and many more) at once. The trade-off is real: a dramatic size reduction, in exchange for a reduced feature set and occasionally different flag behavior than the full GNU version of the same command — a script written assuming GNU-specific sed or grep flags can behave differently under BusyBox's own trimmed implementation.

OpenRC — Delivering on Chapter 1's Own Named Exception

Alpine uses OpenRC rather than systemd, consistent with its broader minimalism-first philosophy — systemd bundles a much larger set of daemons and components alongside pure init functionality, exactly the kind of added surface area Alpine's own design goal explicitly avoids. Chapter 8 covers init systems across all four families in full; this is the "real, living exception" that chapter (and Chapter 1) already named.

apk — Alpine's Own Package Manager

apk add, apk del, and apk update round out Alpine's own package tooling — small, fast, and consistent with the same minimalism running through every other component covered so far.

Why Alpine Dominates Docker Base Images

A full Ubuntu base image commonly runs 70+ MB; Alpine's own base image is typically in the 5–8 MB range — a direct, concrete consequence of musl, BusyBox, and OpenRC all replacing much larger equivalents at once. Smaller images pull faster, deploy faster, and offer a genuinely smaller attack surface — exactly why so many official images on Docker Hub offer a dedicated "-alpine" variant, and why the Docker courses' own image-size and layer-optimization material is really the same underlying theme, just expressed at the individual-image level rather than the whole-OS level this chapter covers.

Hands-On Exercises