Incus: The New LXD

Summary

In this video, the host introduces Incus, a new open-source container and virtual machine manager, derived from Canonical's LXD. Incus focuses on simplicity, improved security, and compatibility across different Linux distributions. Key differences from LXD include a revamped API, token-based authentication, and simplified snapshot management. The video walks through the installation, configuration, and basic container management using Incus, including creating, starting, and bridging containers. Although still in early development (version 0.1), Incus provides an exciting alternative for those seeking a more open-source approach to containerization, with tools available to migrate from LXD.

Takeaways

• 😀 Incus is a community-driven, open-source fork of Canonical's Lex D, designed for system container and virtual machine management.
• 😀 The name 'Incus' is derived from a small bone in the middle ear, symbolizing the project's goal to listen to users and transmit their needs.
• 😀 Incus removes the legacy REST API from Lex D and introduces a new API located at /dev/sl-incus, with better command symmetry.
• 😀 The removal of core trust passwords in favor of tokens and TLS authentication improves the security of the system.
• 😀 Incus simplifies the snapshot process with more intuitive commands like 'incus snapshot create', replacing the complex system in Lex D.
• 😀 The 'incus admin' command introduces more straightforward management commands, such as 'init', 'recover', and 'wait ready', improving usability.
• 😀 Canonical-specific features, such as ShiftFS and Metal as a Service (MAAS) integrations, are removed from Incus to make it more flexible and suitable for various Linux distributions.
• 😀 Incus can be run alongside Lex D on the same server, allowing for smoother transitions between the two platforms for users migrating.
• 😀 The Lex D to Incus Tool allows users to convert containers from Lex D versions 4 to 5.18, making it easier to transition to Incus.
• 😀 Incus is currently at version 0.1 (October 2023) and is still in early development, not yet recommended for full production use but useful for testing and experimentation.

Q & A

What is Incus?

Incus is an open-source container and virtual machine management system, which is a community fork of Canonical's LXD. It is part of the Linux Containers project and offers enhanced security and usability compared to LXD.

Why was the name 'Incus' chosen for this project?

The name 'Incus' was chosen because it refers to a bone in the middle ear, which transmits vibrations, symbolizing the system's purpose of listening to its users and responding accordingly.

How does Incus differ from LXD?

Incus removes legacy APIs that LXD previously used, such as the old REST API, and replaces them with more modern, secure authentication methods like tokens and TLS. It also simplifies the process of creating and managing snapshots and containers.

What is the major change in authentication in Incus compared to LXD?

Incus has removed the use of the 'trust password' in favor of using tokens, TLS, or external authentication methods, offering a more secure approach to managing container access.

What does the 'incus snapshot' subcommand do?

The 'incus snapshot' subcommand allows users to create, delete, list, rename, and restore snapshots of containers. This replaces the more convoluted snapshot management process in LXD, offering greater command symmetry.

How do 'incus admin' commands differ from LXD's commands?

The 'incus admin' commands, such as 'incus admin cluster init', 'incus admin recover', and others, replace older LXD commands like 'lxd init', simplifying and streamlining the container management process.

What happened to Ubuntu-specific features like ShiftFS and MAAS in Incus?

Ubuntu-specific features like ShiftFS (for UID and GID mapping) and MAAS (Metal as a Service integration) have been removed from Incus, as the project aims for a more generalized, open-source solution rather than a Canonical-specific one.

Can Incus and LXD run on the same server?

Yes, Incus and LXD can run on the same server, though they should use different storage pools and network bridges to avoid conflicts.

What tool is available for migrating containers from LXD to Incus?

There is a tool available that allows migration from LXD to Incus. This tool can convert containers from LXD versions 4.x and up to the current Incus version, making it easier for users to transition between the two systems.

What are the steps for setting up a container with a bridge to the main network in Incus?

To set up a container with a bridge to the main network, you first create a profile using the 'incus profile create' command, then add a bridge device to the profile with 'incus profile device add'. After this, you launch the container with the new profile, allowing it to connect to the main network.