Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Import iocage basejails as Bastille thin jails
I think these are the same concept, but with slightly different execution. The main idea is to have a central base system that is shared (readonly) among multiple jails. When this base system is updated, all the jails that reference it immediately see the new system files. This is implemented in iocage as a set of individual zfs mounts, one per system directory. In Bastille, each system directory is symlinked into a subdirectory of a single zfs mount. My test plan here was to import an exported iocage basejail and verify that its Bastille version has the right fstab and symlink changes: ``` Validating file: ssl_2021-11-19.zip... File validation successful! Importing 'ssl' from foreign compressed .zip archive. Archive: ssl_2021-11-19.zip extracting: ssl_2021-11-19 extracting: ssl_2021-11-19_root Receiving ZFS data stream... Generating jail.conf... Updating symlinks... ln: usr/src: Directory not empty Warning: directory usr/src on imported jail was not empty and will not be updated by Bastille Container 'ssl' imported successfully. ```
- Loading branch information