Flatcar Container Linux

Definition

Flatcar Container Linux is a minimal, container-optimized Linux distribution descended from the discontinued CoreOS Container Linux project, designed to run containerized workloads with an immutable root filesystem and automatic, image-based updates. It excludes a traditional package manager, expecting nearly all application software to run inside containers rather than being installed directly on the host, and it is commonly used as the underlying node operating system for Kubernetes clusters across multiple cloud providers and on-premises data centers.

Overview

Flatcar Container Linux emerged after Red Hat discontinued CoreOS Container Linux following its acquisition of CoreOS, with the Flatcar project forked from the same codebase to continue serving users who depended on it, later coming under the stewardship of Kinvolk and then Microsoft after Kinvolk's acquisition. The distribution preserves the core CoreOS philosophy: a minimal, read-only root filesystem, no package manager for host-level software, and container orchestration tools like Docker or containerd as the primary way to run applications. The project maintains both a stable release channel for production use and beta and alpha channels that let operators test upcoming changes before they reach systems running production workloads. Mechanically, Flatcar updates itself using an A/B partition scheme similar in concept to Bottlerocket's: the operating system downloads a full new image to a secondary partition, then reboots into it, allowing safe rollback if the new version fails to boot correctly. Updates can be coordinated across a cluster using a companion component, historically called locksmith, so that machines reboot for updates in a staggered fashion rather than all at once, preventing an entire fleet from going down for maintenance simultaneously. Configuration at boot time is handled through Ignition, a declarative provisioning tool that sets up users, disks, and systemd units before the OS fully starts. Flatcar competes directly with Bottlerocket and Talos Linux in the container-optimized operating system category, and also serves as an alternative base for Kubernetes distributions that historically used CoreOS, such as early versions of Tectonic. Compared to a general-purpose distribution running Docker on top, Flatcar removes the host-level package management surface entirely, pushing teams to containerize everything, which is a stricter operational discipline than optional containerization on Ubuntu or Debian. In practice, Flatcar is deployed as the node OS for self-managed Kubernetes clusters, especially in on-premises or multi-cloud environments where teams want a consistent, minimal, auto-updating host across AWS, Azure, GCP, bare metal, or OpenStack without depending on a single cloud vendor's proprietary node image. The main limitation is the same rigidity that gives it its security benefits: without a host package manager, any tooling that assumes traditional Linux server administration must be containerized or run through Ignition-based provisioning, which adds a learning curve for teams unfamiliar with immutable infrastructure patterns. Organizations moving from a traditional, mutable server fleet to Flatcar typically need to invest upfront in containerizing tooling that previously ran directly on the host, and staff accustomed to logging into a server for ad hoc fixes need to adjust to a fully declarative operating model instead.

Key Features

• Immutable, read-only root filesystem with no host-level package manager
• A/B partition updates with automatic rollback on boot failure
• Ignition-based declarative provisioning at first boot
• Cluster-aware, staggered reboot coordination during updates
• Descended from the discontinued CoreOS Container Linux codebase
• Vendor-neutral support across AWS, Azure, GCP, bare metal, and OpenStack
• Designed around containerd and Docker as the primary application runtime

Use Cases

Alternatives

Frequently Asked Questions

Related in DevOps