runj 0.2.0 adopts new OCI Runtime Spec 1.3.0 with FreeBSD support

runj 0.2.0 now supports the new OCI Runtime Spec 1.3.0, which includes official FreeBSD support!

This is a huge milestone. The new FreeBSD config object closely mimics the jail(8) parameter names. This is different from the original extension runj had implemented, but it should be a straightforward adaptation for anyone already using runj. To aid in compatibility, runj still supports its old config format in runj.ext.json (though this will likely be dropped in a future release).

The announcement from the FreeBSD foundation calls this a “watershed moment,” which is an incredible compliment. I’m proud that runj was the first viable proof-of-concept to bridge the larger container ecosystem with FreeBSD.

Seeking new contributors and maintainers

runj started as a personal learning project, with no expectation of contribution by others (and a policy that discouraged it). When interest in FreeBSD jails as an OCI runtime increased, runj moved to a more-open policy.

The sustained interest in FreeBSD jails and containers over the past few years (2021-2025) has been fantastic, but I haven’t been able to dedicate the time needed to truly grow and maintain runj.

With the OCI Runtime Spec now officially supporting FreeBSD, the timing couldn’t be better to formally welcome new contributors and maintainers!

I need your help to make runj successful:

• If you’re interested in writing code and building features for runj (and containerd on FreeBSD), please come join me!
• If you’re seeking a role with more responsibility, helping guide the development, direction, and long-term success of runj, please reach out to me privately.

I’m really exicted to build the next generation of FreeBSD container tooling with you!