Welcome to Flatcar Container Linux documentation
Flatcar Container Linux runs on most cloud providers, virtualization platforms and bare metal servers. Running a local VM on your laptop is a great dev environment. Following the Quick Start guide is the fastest way to get set up.
Ignition is the recommended way to provision Flatcar Container Linux at first boot. Ignition uses a JSON configuration file, and it is recommended to generate it from the Container Linux Config YAML format, which has additional features. The Container Linux Config Transpiler converts a Container Linux Config to an Ignition config.
¹ These platforms are not officially supported and releases are not tested.
| Bare Metal | Upgrading from CoreOS Container Linux |
|---|---|
| Using Matchbox | Migrate from CoreOS Container Linux |
| Booting with iPXE | Update from CoreOS Container Linux directly. |
| Booting with PXE | |
| Installing to Disk | |
| Booting from ISO | |
| Root filesystem placement |
Follow these guides to connect your machines together as a cluster. Configure machine parameters, create users, inject multiple SSH keys, and more with Container Linux Config.
| [Configuring date & timezone][date-timezone]
| [Adding users][users]
| [Kernel modules / sysctl parameters][parameters]
Flatcar Container Linux supports all of the popular methods for running containers, and you can choose to interact with the containers at a low-level, or use a higher level orchestration framework. Listed below are your options from the highest level abstraction down to the lowest level, the container runtime.
| Docker |
|---|
| Getting started with Docker |
| Customizing Docker |
APIs and troubleshooting guides for working with Flatcar Container Linux.