Why Linux Dominates the Cloud: A Story of Accidents and Lock-In

If you’ve ever deployed a cloud server, you’ve almost certainly used Linux. It runs AWS, Azure, Google Cloud, and most of the internet. But here’s the thing: Linux didn’t win the cloud because it was the best OS in 2000. It won because of a series of historical accidents, architectural advantages, and business decisions that slowly locked the industry into a Linux-first world.

The Cloud’s Birth Wasn't Linux-Native

When Amazon launched EC2 in 2006, the cloud was a weird experiment. The original EC2 ran on a heavily modified Red Hat Linux kernel inside Xen hypervisors. Why Linux? Not ideology—pragmatism. Amazon needed a free OS they could legally bundle, strip down, and re-sell as a service. Windows Server cost licenses per instance. Linux cost zero.

But the real lock-in happened deeper: the Linux kernel’s driver ecosystem. Cloud hardware—NICs, SSDs, and virtualization features—needed kernel modules. Linux had them, because the kernel community had already absorbed drivers from every vendor imaginable. Windows Server required Microsoft to write drivers, which they did slowly. Linux was already there.

The Snowball Effect of Open Source Tooling

In the early 2000s, LAMP stacks (Linux, Apache, MySQL, PHP/Perl/Python) dominated web hosting. When cloud providers started offering virtual machines, developers naturally moved their LAMP apps. Cloud-native tooling was then built on top of Linux, not ported to free BSD or Windows.

Consider these milestones:

• Chef (2009) and Puppet (2005) – born on Linux, only later supported Windows half-heartedly.
• Docker (2013) – used Linux kernel features (cgroups, namespaces) that Windows didn’t have until 2016.
• Kubernetes (2014) – designed for Linux containers first. Windows support arrived years later and is still second-class.

Each new tool reinforced Linux’s position. If you wanted modern ops, you went Linux.

Why Microsoft Ultimately Gave Up

By 2014, Microsoft realized they couldn’t fight the cloud tide head-on. Azure had launched in 2010 with Windows VMs, but customers kept asking for Linux. Satya Nadella’s “Microsoft loves Linux” strategy wasn’t just marketing—it was survival.

Microsoft invested heavily in Linux compatibility: native SSH in Windows, WSL (Windows Subsystem for Linux), and running Linux containers on Azure. But here’s the catch—they were forced to run Linux inside their own cloud. Today, over 60% of Azure’s VMs run Linux. The server OS that once competed with Windows now runs on top of it.

What Linux Couldn’t Do (And Still Can’t)

Linux’s cloud dominance has limits. It never conquered the desktop, and it struggles in niche enterprise databases that require Windows-only SQL Server features (though that gap is closing). More importantly, Linux fragmented: Ubuntu, CentOS, Debian, and RHEL all have slightly different package managers and init systems. Cloud providers hated supporting three different distros, so they standardized on a common base image.

The real winner wasn’t Linux per se—it was the Linux kernel + systemd + a minimal distribution model. Most cloud VMs run a stripped-down Ubuntu LTS or Amazon Linux, which is just Red Hat with AWS branding.

The Hard Truth: Lock-In Through Simplicity

The final reason Linux won is boring: it was cheap enough and good enough. No cloud provider wanted to pay OS licensing fees per VM. No developer wanted to learn Windows Server internals just to deploy a web app. Linux offered a consistent API (POSIX), zero cost, and a massive ecosystem of battle-tested open-source software.

Twenty years later, we don’t choose Linux for the cloud. The cloud chooses Linux for us.