Incus is a modern, secure and powerful system container and virtual machine manager.
It provides a unified experience for running and managing full Linux systems inside containers or virtual machines. Incus supports images for a large number of Linux distributions (official Ubuntu images and images provided by the community) and is built around a very powerful, yet pretty simple, REST API. Incus scales from one instance on a single machine to a cluster in a full data center rack, making it suitable for running workloads both for development and in production.
Incus allows you to easily set up a system that feels like a small private cloud. You can run any type of workload in an efficient way while keeping your resources optimized.
You should consider using Incus if you want to containerize different environments or run virtual machines, or in general run and manage your infrastructure in a cost-effective way.
You can try Incus online at: https://linuxcontainers.org/incus/try-it/
Incus, which is named after the Cumulonimbus incus or anvil cloud is a community fork of Canonical's LXD.
This fork was made in response to Canonical's takeover of the LXD project from the Linux Containers community.
The main aim of this fork is to provide once again a real community project where everyone's contributions are welcome and no one single commercial entity is in charge of the project.
A migration tool called lxd-to-incus is provided to aid with migrating an existing LXD environment over to Incus.
See Getting started in the Incus documentation for installation instructions and first steps.
- Release announcements:
https://discuss.linuxcontainers.org/c/news/ - Release tarballs:
https://github.com/lxc/incus/releases/ - Documentation:
https://linuxcontainers.org/incus/docs/main/
| Type | Service | Status |
|---|---|---|
| Tests | GitHub |  |
| Go documentation | Godoc |  |
| Static analysis | GoReport |
Consider the following aspects to ensure that your Incus installation is secure:
- Keep your operating system up-to-date and install all available security patches.
- Use only supported Incus versions.
- Restrict access to the Incus daemon and the remote API.
- Do not use privileged containers unless required. If you use privileged containers, put appropriate security measures in place. See the LXC security page for more information.
- Configure your network interfaces to be secure.
See Security for detailed information.
IMPORTANT:
Local access to Incus through the Unix socket always grants full access to Incus. This includes the ability to attach file system paths or devices to any instance as well as tweak the security features on any instance.
Therefore, you should only give such access to users who you'd trust with root access to your system.
The following channels are available for you to interact with the Incus community.
You can file bug reports and feature requests at: https://github.com/lxc/incus/issues/new
Community support is handling at: https://discuss.linuxcontainers.org
Commercial support is currently available from Zabbly for users of their Debian or Ubuntu packages.
The official documentation is available at: https://github.com/lxc/incus/tree/main/doc
Fixes and new features are greatly appreciated. Make sure to read our contributing guidelines first!