LXD (Linux Container Daemon) is a container and virtual machine management tool
Some days ago Canonical announced, through a blog post, the release of the new version of the container manager LXD 5.16 and 5.17 and of the most notable changes, the most important is in LXD 5.17 with support for OpenZFS 2.2 delegation, among other things.
For those who are unaware of LXD, you should know that this provides tools to centrally manage containers Deployed in multi-server clusters. LXD is implemented as a background process, accepts network requests via the REST API, and supports multiple storage backends, snapshots with a state segment, live migration of running containers from one machine to another, and tools for store image containers.
El Kit LXC tools it serves as tiempo of execution for lanzar containers and includes the library liblxc, un set of utilities (lxc-create, lxc-start, lxc-stop, lxc-ls, etc.), templates for can bring to life containers and a set of various programming language links. Isolation is carried out using standard Linux kernel mechanisms (namespaces, cgroups, Apparmor, SELinux, Seccomp). In addition to LXC, LXD also uses components from the CRIU and QEMU projects.
Main news of LXD 5.17
In this new version that is presented of LXD 5.17, it is highlighted that Introduces the ability to delegate namespaces to ZFS, allowing a container access to manage its data set on ZFS. And it is expected that the stable version of OpenZFS 2.2 will be released soon, since many new features are expected with this open source ZFS file system for Linux and BSD systems.
Another change that stands out in this new version is that Support for copying a snapshot of a partition to another host has been added to the toolkit and create a new partition on it, as well as added detection of unknown storage groups and recreation of database logs to the disaster recovery utility.
In addition to this, it is also noted that documentation was improved, changed to Diataxis navigation style, added a procedure to add a routed NIC to a VM instance, changed configuration options sections to be collapsible and linkable.
It is also highlighted that updated lxd-doc to support yaml type assertion, added a test for export, import and recovery of backups, installed additional packages to enable PKI and simultaneous executive tests.
On the part of the changes that were made in the LXD 5.16 version, the following is highlighted:
- It is now possible to load ISO image files as custom storage volumes, which can be attached to a virtual machine as a bootable CD disk, allowing for simplified installation of custom operating systems from a “library” of custom ISO volumes .
- LXD implementations allocate and consume IP addresses for various purposes. But until now there was no easy way for external systems (such as IPAM applications) to identify and track the use of these addresses. LXD now features a new unified endpoint that aggregates all network mappings. In addition to the new API endpoint (/1.0/network-allocations endpoint 1 ), there is also an attached CLI command lxc network list-allocations that will display your IPAM information.
- Some entity types in LXD have the concept of properties that are separate from the configuration options of that entity. Previously, the only way to modify these properties was to do so interactively with the lxc * edit commands or by a combination of lxc * show piped to sed/awk and then back to the appropriate lxc * edit command. It is now possible to modify an entity property directly with the lxc * set commands by providing the –property flag.
Finally, if you are interested in knowing more about it, you can check the details in the following link