Compare

JailOps vs iocage

iocage is the jail manager many FreeBSD users learned on: a Python tool built around ZFS, with fast jail creation and snapshots. Its upstream repository was archived by its owner in April 2024, so it takes no new changes there, though the FreeBSD ports tree still carries a port of it. If you run iocage today, this page is about what you get when you move.

Side by side

JailOps and iocage side by side
JailOpsiocage
ShapeA daemon with an HTTP API, a CLI and a web consoleA command line tool
Written inGo, static binariesPython 3
StatusDeveloped in the openUpstream repository archived (read-only) since April 2024
NetworkingRouted: the host hands out addresses and keeps jails apart, no bridge, no DHCPVNET and shared-IP jails
StorageZFS, with snapshots and rollback and volumes as objectsZFS, with snapshot management and export and import
PlatformFreeBSD 15.1 and laterFreeBSD 11.4 and later according to its readme, and HardenedBSD

Facts about iocage come from its own site and repository. Check them there for the latest.

Where iocage is stronger

  • A long history. Many guides, many setups, and a lot of people who know it.
  • Simple to start. One tool, a short command syntax, jails in seconds.
  • Older releases. It targets FreeBSD 11.4 and later, while JailOps needs 15.1.

Where JailOps is stronger

  • It is maintained. New FreeBSD releases, security fixes and features arrive, and the project is open about what is coming on the roadmap.
  • An API and a console on top of the CLI, and projects to keep teams apart.
  • Networking handled by the host. Addresses are handed out and every jail has a routed link of its own, so jails are kept apart without a bridge or a DHCP server.
  • Firewall policies you can test, encrypted jails, volumes shared between jails, and backups that include the volumes.
  • Managed updates with a snapshot first and a way back. See the life of a jail.

Which to pick

Pick iocage if you run a release older than 15.1 that you cannot move yet, or a stable setup that you have decided not to touch.

Pick JailOps if you want a jail manager that keeps up with FreeBSD, with an API, projects and a console, and a clear way to run many jails.

The two can live on different hosts. Nothing stops you from trying JailOps on one machine and keeping the rest as they are.

See it on your own host.

Look at the console on demo data, or install on a clean FreeBSD 15.1 machine.