A FreeBSD jail should be small.
-
A FreeBSD jail should be small. Installing Python into every jail just so your config management can run is the tail wagging the dog.
I wrote two tiny wrappers to plug cdist directly into jexec on the host.
The result? Full configuration management that asks for nothing but POSIX sh inside the jail itself. Zero daemons. Zero agents.
https://blog.hofstede.it/automating-freebsd-jails-with-cdist-zero-dependencies-inside-the-jail/
My cdist-jexec connection plugin scripts: https://codeberg.org/Larvitz/jexec-cdist
-
A FreeBSD jail should be small. Installing Python into every jail just so your config management can run is the tail wagging the dog.
I wrote two tiny wrappers to plug cdist directly into jexec on the host.
The result? Full configuration management that asks for nothing but POSIX sh inside the jail itself. Zero daemons. Zero agents.
https://blog.hofstede.it/automating-freebsd-jails-with-cdist-zero-dependencies-inside-the-jail/
My cdist-jexec connection plugin scripts: https://codeberg.org/Larvitz/jexec-cdist
@Larvitz Amazing!
-
A FreeBSD jail should be small. Installing Python into every jail just so your config management can run is the tail wagging the dog.
I wrote two tiny wrappers to plug cdist directly into jexec on the host.
The result? Full configuration management that asks for nothing but POSIX sh inside the jail itself. Zero daemons. Zero agents.
https://blog.hofstede.it/automating-freebsd-jails-with-cdist-zero-dependencies-inside-the-jail/
My cdist-jexec connection plugin scripts: https://codeberg.org/Larvitz/jexec-cdist
@Larvitz I love this philosophy. Ansible gets pretty annoying cuz you need dependencies on the host for many things. Being able to “compile” to a common target like POSIX shell makes perfect sense.
