v1.4.0
This release brings improved behavior of the initial_setup
script when creating new jails from config templates. This release does not introduce any changes in how existing jails are treated. In general there should be no breaking changes. But if you have your own, custom, config templates you may want to read carefully if this release impacts your initial_setup
script. You can simply replace jlmkr.py to upgrade to the latest version.
What's Changed
- The
initial_setup
script will now run once the jail has been startup for the first time and will wait for the init system and networking to be ready. It used to run BEFORE the first start using the host networking namespace and without applying thesystemd_nspawn_user_args
. This had several downsides, such as the inability to install some packages, not being able to access bind mounts from theinitial_setup
script and inconsistent networking modes. The new behavior fixes this. - Config templates now default to bridge networking, please see the updated docs on how to set up bridge networking.
- The docker config template will now also install the NVIDIA Container Toolkit if
gpu_passthrough_nvidia=1
when the jail starts for the first time. - Updated experimental lxd and incus templates to take advantage of the improved
initial_setup
behavior. - Fixes in the podman rootless install instructions as well as the config template.
Full Changelog: v1.3.0...v1.4.0