Flake Pilot User Guide

Application Isolation - Secure Execution with a Native Feel

Flake Pilot registers, provisions and launches applications that are not installed on your host but are provided inside a runtime environment such as an OCI container or a Firecracker virtual machine. The registered application behaves like any other program on the system: it is called by its name, it reads and writes the data you point it to, and it returns its exit code to your shell. Everything that is needed to run it, the image, the engine and the provisioning of the instance, is handled behind that name.

An application registered this way is called a flake.

Flake Pilot architecture overview

About This Guide

This guide is written for administrators and developers who want to provide isolated applications on a Linux host. It explains the concepts behind flakes, shows how to register applications for the podman and firecracker engines, describes the network setup for virtual machines and documents the layout of the flake configuration.

The guide is organized as follows:

The command line of each tool is documented in the manual pages shipped with the packages, e.g man 8 flake-ctl or man 8 podman-pilot. This guide references them where the details matter.

Resources

Feedback is very much welcome.