Why Docker Dominates Cloud Computing by Reusing Decades‑Old Technologies

1. The Myth of a New Technology

Docker was launched in 2013 and now hosts over 14 million images, serves more than 11 billion pulls per month, and appears in millions of GitHub repositories, yet it did not invent any core technology. Its functionality is built on components that existed decades earlier.

2. The Legacy Building Blocks

chroot – introduced in Unix V7 (1978).

Filesystem namespace – added in Linux 2.5.2 (2001).

Network namespace – added in Linux 2.6.24 (2007).

Layered image format – essentially tar‑over‑tar.

Running Linux containers on macOS/Windows – uses the ancient SLIRP tool originally written for PalmPilot dial‑up networking in the mid‑1990s.

Cross‑CPU execution – relies on QEMU together with the obscure binfmt_misc kernel feature.

These “old‑timer” components are combined to form Docker’s container stack.

3. The Perfect‑Solution Graveyard

Compared with technically superior alternatives, Docker still wins:

Plan 9 : a complete OS redesign that would require the world to rewrite its operating system. Docker wins because it works on existing Linux.

Full virtualization (VMs) : provides stronger isolation but incurs a startup penalty of dozens of seconds, making it unattractive for everyday developer workflows. Docker’s containers start in fractions of a second.

Nix/Guix : elegant, reproducible package managers that demand a wholesale repackaging of all software. Docker lets developers keep their current build tools and simply add a few Dockerfile lines.

4. Minimal Change, Maximum Adoption

A developer who wants to run a Python web app can keep using pip and the usual project layout; the only new step is writing a Dockerfile:

FROM python:3
COPY requirements.txt /app/requirements.txt
WORKDIR /app
RUN pip install -r requirements.txt
COPY . /app
EXPOSE 80
CMD ["python", "app.py"]

After docker build, docker push, and docker run, the application runs on any machine with Docker installed, without learning a new configuration language or understanding kernel namespaces.

5. The SLIRP Legend

When Docker for Mac needed to run Linux containers on macOS, the straightforward solution was to ship a full VM. Instead, Docker embedded a complete Linux kernel inside the desktop app (using HyperKit) and routed container network traffic through SLIRP, a user‑space TCP/IP stack from the 1990s. This avoided bridge networking, bypassed enterprise firewalls, and reduced bug reports from thousands to a few dozen—a >99 % drop.

6. The Pragmatic Engineering Law

Success in the real world depends less on technical perfection and more on how little a solution forces the existing ecosystem to change. Docker’s stack is a “code‑style” patchwork: a 1978 chroot foundation, a series of namespace patches added between 2001‑2007, a 1990s SLIRP networking layer, QEMU for CPU translation, and overlayfs copy‑on‑write for the filesystem.

Despite being a “building code violation,” this patchwork houses millions of developers, while the theoretically cleaner Plan 9 design remains empty.

7. Component Decomposition and Ongoing Dominance

Since 2016 Docker has split its monolithic daemon into independent components: containerd (runtime), BuildKit (image building), and dockerd (orchestration). The stated goal was to let the community replace each piece, yet no alternative has displaced Docker because the whole stack hides complexity behind a simple surface.

8. Keeping Up with New Workloads

When GPU workloads arrived, Docker added the Container Device Interface (CDI) as another patch: it injects the required driver files and libraries at container start‑up instead of trying to create a universal GPU abstraction layer.

9. Conclusion

Docker’s repeated victories all share a single cause: it chose the path of “no new invention.” By reusing chroot, namespaces, SLIRP, QEMU, and other legacy mechanisms, Docker lets developers keep their habits while solving a massive deployment problem, proving that the most pragmatic, “good‑enough” engineering often wins over technically superior designs.