* Adding k3s example
---------
Co-authored-by: Javy de Koning <javydekoning@gmail.com>
Co-authored-by: Jip-Hop <2871973+Jip-Hop@users.noreply.github.com>
Updated config templates to benefit from initial_setup running after jail has fully started.
Added conditional nvidia-container-toolkit install during initial_setup.
Config templates now default to bridge networking.
First jail startup will now wait for init system and networking to be ready before running the initial_setup script inside the jail. All systemd_nspawn_user_args are now applied and the initial_setup script will have access to filed mounted via bind mounts.
* Follow Debian guidelines for launching editors
When jailmaker wants to ask the user to edit a file, mostly a jail
config, it currently uses `nano`. This is not how a program is supposed
to work according to [Debian's guidelines]. This changes the hardcoded
`nano` to look up the correct editor to use using environmental
variables.
[1]: https://www.debian.org/doc/debian-policy/ch-customized-programs.html#editors-and-pagers
* Bump version to 1.3.0
---------
Co-authored-by: Jip-Hop <2871973+Jip-Hop@users.noreply.github.com>
by ignoring the .lxc and jails directories it means that the jlmkr script can be
run directly from a checkout, complete with documentation and templates
Added Full ZFS Dataset Support:
- The script will now create a ZFS dataset for each jail if the 'jailmaker' directory is a ZFS dataset
- The script will create the 'jails' directory as a dataset if the 'jailmaker' directory is a ZFS dataset
- The script will now remove the ZFS dataset (including snapshots) when deleting the jail
- Dual mode: For legacy use without datasets, it will continue to work as previously
Added a guide to migrate from using directories to using ZFS datasets.
Closes#80.
---------
Co-authored-by: Jip-Hop <2871973+Jip-Hop@users.noreply.github.com>
Jip-Hop