Incus 7.0 LTS: What You Need to Know

Incus 7.0 LTS, the latest long-term-support release of the container and virtual-machine management platform, is now available. This version introduces several key enhancements, including a low-level backup API, native S3 operations to replace the unmaintained MinIO project, and drops support for cgroups v1 and xtables (iptables/ip6tables/ebtables). With support guaranteed through June 2031, the release promises a steady stream of updates: two years of full bug and security fixes complemented by minor usability improvements, followed by three years of security-only maintenance. Community contributions remain strong, with 204 individuals involved since the 6.0 LTS release. Below, we answer the most common questions about this milestone update.

What is Incus 7.0 LTS?

Incus 7.0 LTS is a long-term-support version of the Incus system for managing containers and virtual machines. It represents a stable release that will receive ongoing maintenance and security updates for a total of five years, specifically until June 2031. The first two years include bug fixes, security patches, and minor usability improvements delivered through point releases (e.g., 7.0.1, 7.0.2). After that period, only critical security fixes will be provided for the remaining three years. This makes Incus 7.0 LTS ideal for production environments requiring a predictable, stable platform over an extended timeframe.

What are the major new features in Incus 7.0 LTS?

Two standout additions are the low-level backup API and basic S3 operations integrated directly into Incus. The backup API gives administrators finer control over creating and managing snapshots and backup data, enabling automated workflows. The S3 operations feature allows Incus to handle basic object storage tasks—such as storing and retrieving container images—without relying on external tools like MinIO, which is no longer maintained. This reduces dependencies and simplifies system architecture.

Why was S3 support added, and what replaces MinIO?

Incus previously depended on MinIO (an open-source object storage server) to manage S3-compatible operations, such as hosting container images. However, the MinIO project entered an unmaintained state within the Incus ecosystem. To avoid relying on unsupported external software, the development team built basic S3 capabilities directly into Incus 7.0 LTS. This built-in implementation covers common operations like bucket creation, object listing, and retrieval—enough to replace MinIO for typical Incus workflows. As a result, users enjoy a more self-contained and future-proof solution.

What support was removed in this release?

Incus 7.0 LTS drops support for cgroups v1 and the xtables firewall frameworks (iptables, ip6tables, ebtables). cgroups v1 is the older version of Linux control groups; its removal encourages users to migrate to the more efficient cgroups v2. Similarly, xtables has been superseded by nftables for modern packet filtering. Removing these legacy components simplifies the codebase, reduces maintenance overhead, and aligns Incus with current Linux kernel developments. Users still relying on these older systems must upgrade their environments before deploying Incus 7.0 LTS.

How many contributors worked on Incus 7.0 LTS?

A total of 204 individuals contributed to Incus between the 6.0 LTS and 7.0 LTS releases. This count includes code contributions, translations, documentation, and other project improvements. Of these, 45 people were directly active between the 6.23 milestone and the final 7.0 LTS release. The broad community involvement reflects the project’s health and the collaborative effort behind delivering a stable long-term support version. Each contributor helped refine features, fix bugs, and ensure the platform meets the needs of its diverse user base.

What is the support timeline for Incus 7.0 LTS?

Support for Incus 7.0 LTS lasts until June 2031—a total of five years. The first two years (ending mid-2028) are the “active” phase, during which point releases (e.g., 7.0.1, 7.0.2) deliver not only critical security fixes and bug patches but also minor usability improvements. After that, the release enters a “security-only” maintenance phase for the remaining three years (until June 2031). This phased approach allows users to plan upgrades confidently, knowing they will receive timely fixes for vulnerabilities while avoiding disruptive feature changes in later stages.

Should I upgrade to Incus 7.0 LTS?

If you are running an older Incus version (especially 6.0 LTS or earlier), upgrading to 7.0 LTS is strongly recommended. The new long-term support cycle provides a stable foundation through 2031 with a clear maintenance roadmap. Moreover, the removal of deprecated features (cgroups v1, xtables) and the inclusion of the built-in S3 support and backup API improve security and reduce external dependencies. Ensure your host systems run compatible kernels with cgroups v2 and nftables before upgrading. For those starting fresh, Incus 7.0 LTS offers the most reliable and forward-looking platform available today.