I've been using ezjail for about as long as I can remember. The main reasons for this are:
So, that said, what are other people using? Oddly enough, ezjail is still offered up in the Handbook as an option (https://www.freebsd.org/doc/handbook/jails-ezjail.html), but I think that's just a delay.
In an ideal world either the project would have adopted something like ezjail into base to make jails easier to use or crafted a replacement, but I'm not holding my breath.
I'm open to any options, but the short list of requirements would be:
- ZFS integration - single command creates the jail and all dataset(s) needed, sets quotas (if desired)
- single command to create a jail, and generally no configuration files to manage on an ongoing basis
- shared "base" system, which originally was handy for saving space (and is again for cloud hosting or other limited disk space situations)
- shared "base" is handy for upgrades, upgrade from 1 to 100 jails in one fell swoop
- fairly sane configuration files if you need to override basics
- very flexible network configuration exposed in config files - easy to add multiple IPs, specify interface binding for IPs, etc.
So, that said, what are other people using? Oddly enough, ezjail is still offered up in the Handbook as an option (https://www.freebsd.org/doc/handbook/jails-ezjail.html), but I think that's just a delay.
In an ideal world either the project would have adopted something like ezjail into base to make jails easier to use or crafted a replacement, but I'm not holding my breath.
I'm open to any options, but the short list of requirements would be:
- replicate all the ezjail benefits noted above
- not be qjail (the author stole ezjail and claimed it as his own: http://erdgeist.org/posts/2017/dont-piss-in-my-beer.html)
- not rely on much more than the base system to operate (no python, perl, php or any other nonsense - security-sensitive software should be simple)