The goal of Cells for NetBSD was to provide a pragmatic middle ground for NetBSD between simple chroot setups and full virtualization.
This was never meant to replicate Linux container ecosystems. The focus was a NetBSD-native model with clear operational boundaries:
I implemented a layered architecture with clear responsibilities:
secmodel_cell as the kernel foundation for identity, isolation, and policy enforcementcellctl as the runtime-near interface for lifecycle actions and snapshot metricscellmgr as the unified control plane for desired state, runtime state, reconciliation (apply), and backup/restorecellui as an interactive TUI for operational workflowsThe operating model is declarative at its core:
manifests describe the full target state, and cellmgr apply converges the system to that state in a repeatable way.
To validate practical viability, I also built and operated end-to-end stacks under realistic conditions, including a MantisBT stack (PostgreSQL, php_fpm, nginx) and a Luanti server scenario.
Cells for NetBSD has evolved from a pure isolation prototype into a cohesive operating model:
cellmgr applyIn parallel, project documentation is continuously expanded, including man pages and practical end-to-end recipes.
Project page: https://netbsd-cells.petermann-digital.de/
secmodel_cell, kauth)cellctl, cellmgr, celluiCells for NetBSD stands for a deliberately lean, NetBSD-native isolation approach: clear states, clear tools, clear operations.
With Cells for NetBSD, I combine kernel-level isolation with a clear and reproducible operating model - from secmodel_cell up to daily operations with cellmgr and cellui.
Get in touch