FreeBSD Containers and Orchestration

FreeBSD introduced its container, OS-level virtualization primitive in 1999 in the form of a security-oriented isolation framework and subsystem called Jails. Similar to OpenVZ Containers in 2005, Solaris Zones, LXC, Docker and other implementations, FreeBSD Jails allow isolation of applications or entire stacks with their own processes, filesystems and users, whilst using the same host operating system kernel.

Container Tools: Base System

Out of the box, FreeBSD provides:

Container Tools: Third-Party

These third-party tools aim to simplify and speed up the process of creating and managing FreeBSD jail-based containers on individual hosts, and many include additional support and integration for FreeBSD features such as bhyve virtualization, ZFS, Virtual Networks (VNET), Templating, Import/Export among others.

AppJail

Jail framework written in C and posix shell to create, deploy and maintain jail-based containers.

Tools:

Supports:

Podman, Buildah

A FreeBSD port of the https://github.com/containers stack. Install sysutils/podman-suite from FreeBSD Ports/Packages.

runj / containerd / nerdctl

Experimental FreeBSD Jail execution runtime implementation and FreeBSD OCI specification development.

Supports:

Bastille

Command-line (shell) tool and automation framework for jail-based containers.

Supports:

pot

Command-line (shell) tool for jail-based containers.

Supports:

cbsd

Command-line and TUI (shell) tool for jail-based containers.

Supports:

None of the above orchestration tools have a "run a plain vanilla linux inside the container" feature, but the start/stop/templating feature of them does not prevent a manually created plain-vanilla-linux-jail.

iocage

Command-line (Python, originally shell) tool for jail-based containers.

Supports:

ioc

Re-implementation (Python) of iocage.

iocell

Fork of original (shell) iocage

ezjail

Command-line (shell) tool for jail-based containers.

Supports:

Container Orchestration

The container tools above can be used as a base for multi-host orchestration, by exporting containers from one host, and either moving the container to another host, or by utilising shared storage (eg: SAN) or ZFS to switch container datasets from one host to another and importing it on the target host.

Additionally the following FreeBSD container orchestration tools are available:

Container Orchestration Distributions

XXX: add some FreeBSD derived distributions which have their focus (not only) on container virtualisation.

Working Groups

FreeBSD Cloud Native Containers Technologies

If you are interested in helping to improve the support for cloud native containers on FreeBSD, please come along to the FreeBSD Cloud Native Containers Technologies meeting.

The (draft) goal of the group is "Identify important work needed to make FreeBSD a top-tier choice for running cloud native containerised workloads. Aim to champion these pieces of work to the point where they can "graduate" from this group e.g. have an owner and are being actively worked on."

When and where?

Go to CommunityCalendar

The 45 minute meeting is biweekly on Mondays, starting 2025-09-22 at 16:30 UTC time (NOTE: this time will follow UK daylight savings time, so will go forward an hour in the spring).

Joining instructions

https://us06web.zoom.us/j/87237884069?pwd=VAACINGReoLFkVAu2Fbxr3Kvn7tzja.1

Meeting ID: 872 3788 4069 Passcode: 713475

More ways to join

Meeting notes

https://hackmd.io/xA1CxQT8SfKLUpCiQz-tWA

Containers (last edited 2025-11-27T11:13:54+0000 by AliceSowerby)