LXD 6.1 Debuts with Fresh Network Features

Share it

LXD, an esteemed system container and virtual machine supervisor, is a project housed within the Canonical umbrella, the organization responsible for Ubuntu. This cutting-edge tool offers a user-friendly and fortified approach to overseeing Linux containers, and it has recently unveiled its latest iteration, version 6.1.

For individuals who may not be acquainted with it, LXD expands on LXC (Linux Containers) by integrating a more robust and user-friendly management interface into LXC’s existing capabilities.

LXC, on the flip side, furnishes a machine-like encounter, supporting the full functionality of operating systems within containers, all while leveraging the lightweight and scalable advantages of containerization.

Fresh Additions in LXD 6.1

The advent of LXD 6.1 heralds the inaugural feature release in the 6.x series, ushering in enhancements that elevate functionality and user interaction. One notable aspect is the automatic allocation of IP addresses for OVN (Open Virtual Network) network forwards and load balancers.

This feature streamlines the configuration of network components by autonomously assigning IP addresses, eliminating the necessity for manual selection of available IPs. This automation not only conserves time but also diminishes complexity, particularly in environments where network resource visibility is restricted.

This latest release also fine-tunes virtual machine performance through the process of automatic core pinning. This procedure guarantees that VMs lacking specified CPU cores have their QEMU processes automatically distributed across balanced CPU cores.

However, it is imperative to bear in mind that in systems featuring a mix of performance and efficiency cores, users may encounter a slight performance drop, which can be alleviated by implementing explicit CPU pinning.

An additional highlight of this update is the endorsement of the Dell PowerFlex Storage Data Client kernel driver, now compatible with LXD’s PowerFlex storage pools. This serves as an alternative to NVMe over TCP and necessitates a connection to the Dell Metadata Manager.

From a security vantage point, LXD 6.1 does away with the core.trust_password server setting, fortifying security by discouraging the utilization of enduring shared passwords. Instead, new clients must be incorporated into the LXD API through certificates or join tokens.

Furthermore, this release heightens the scrutiny on container mknod syscall interception capability checks, aligning them more closely with host kernel actions.

It is important to note that LXD 6.1 implements measures to safeguard DNS services within supervised bridge networks by obstructing DNS traffic from external networks to the dnsmasq service, enhancing network insulation and security.

Moreover, it addresses concerns linked to running VMs on hosts containing over 64 CPUs and supports extended and special character-inclusive device names in VMs, thus enhancing compatibility and adaptability in system setups.

Lastly, this release discontinues support for the armhf architecture in anticipation of forthcoming updates and elevates the minimum Go version required to construct LXD to 1.22.4, thereby guaranteeing compatibility with contemporary development environments.

To discover more about all the changes in the LXD 6.1 container manager, refer to the release notification or peruse the complete changelog. The software is downloadable on Linux, MacOS, and Windows platforms.

🤞 Don’t miss these tips!

🤞 Don’t miss these tips!

Solverwp- WordPress Theme and Plugin