JailOps vs AppJail
AppJail is a framework written in shell and C for making portable jails that behave like an application, described with Makejail files. It is in the ports tree and has many features. JailOps is a daemon with an API, projects and a console. The two aim at different ways of working.
Side by side
| JailOps | AppJail | |
|---|---|---|
| Shape | A daemon with an HTTP API, a CLI and a web console | A command line framework with a modular command structure |
| Written in | Go, static binaries | POSIX shell and C |
| License | BSD 2-Clause | BSD 3-Clause |
| Describe a jail | YAML in git, an app catalog | Makejail files, similar in idea to a Dockerfile |
| Networking | Routed: the host hands out addresses and keeps jails apart, no bridge, no DHCP | Virtual networks, bridge, VNET, IPv4 and IPv6 with DHCP and SLAAC, port forwarding, netgraph |
| Storage | ZFS | UFS and ZFS |
| Also | Projects, firewall policies you can test, encrypted jails, Linux jails | OCI container support, health checks, secrets, resource limits, parallel start, PkgBase |
Facts about AppJail come from its own site and repository. Check them there for the latest.
Where AppJail is stronger
- Breadth. Virtual networks, DHCP, SLAAC, netgraph, OCI containers, health checks and secrets are all in the box.
- Makejail. A compact file that builds a jail, easy to share and to read.
- UFS as well as ZFS, if some of your machines do not run ZFS.
- In the ports tree, with recent releases.
Where JailOps is stronger
- One network model. The host hands out addresses and gives every jail a routed link of its own, so jails are kept apart. There is no bridge to design and no DHCP to run, so there are fewer things to get wrong. The cost: there is no layer 2 between jails, so multicast, mDNS and VRRP do not pass from one jail to another.
- An API and a console, with projects that separate teams and customers on one host.
- Firewall policies with a test command and a simulator, so you can see what a rule list does before it matters.
- Volumes as objects and backups that take them once, encrypted jails, and managed updates with a way back.
- Fleets in git. A repository of YAML describes networks, projects and jails, and
jailops-syncapplies it. See fleet examples.
Which to pick
Pick AppJail if you want OCI containers, UFS, or a toolbox of network features, and you like describing jails in Makejail files.
Pick JailOps if you want an API and a console, projects, one simple network model and backups that include the data.
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.