This episode explores the newest LTS release: LXC 7.0 LTS (April 2026) with support until June 2031, cgroup2 maturity, security fixes like CVE-2026-39402, the position of 6.0 moving to slow maintenance, and the release history of 6.0, 5.0, and 4.0.

Throughout this series we've used LXC 7.0 LTS — but we've never broken it down specifically. In episode 17 we do: what the newest LTS release brings, why you should move to 7.0 if you're still on 6.x, and how each release sits in LXC's history. This matters for upgrade decisions and long-term support planning.
LXC 7.0 LTS was released on April 30, 2026 and is the current LTS (Long Term Support) release, supported until June 2031 — a full five years of security and bug fixes. For production, this is the version you should install (and it's the one we installed in episode 3).
lxc --versionlxc.cgroup2.* limits (episode 7) are stable and fully supported.Note
An LTS release isn't about flashy features — its strength is precisely stability and patch guarantees. Vendors and operators (including Proxmox VE 9.2 from episode 12) choose 7.0 for its clear support schedule, not for new features.
LXC 6.0.6 LTS (released February 27, 2026) marks the 6.0 series moving to slow maintenance: no more features or major fixes, only important patches for security and critical bugs. Official support runs until June 2029.
For those still on 6.0: there's no panic urgency, but plan a migration to 7.0 in your next upgrade window. The process is simple — the config format version stays compatible — and you gain a longer patch window (2031 vs 2029).
lxc --versionLXC uses strict semantic versioning and two-yearly LTS releases. The pattern is consistent: an LTS release appears every ~2 years, with point releases in between for fixes and patches. The major version number marks a new LTS; minor and patch mark fixes within a series.
The practical implications:
lxc/lxc repo for each series' EOL schedule.Tip
A sane host strategy: use LTS 7.0 (or newer when it arrives) as your base, keep point releases updated, and put major upgrade windows on your team's calendar. That way no production version ever suddenly runs out of support.
Official sources for confirming versions and patches:
lxc-checkconfig and lxc --version — local verification.lxc --version
lxc-checkconfig > /dev/null && echo "kernel OK"
systemctl is-active lxc-netKey takeaways:
In the next episode 18 we'll cover performance tuning & large scale — choosing the ZFS/btrfs backend for efficient snapshots, tuning cgroups for density, per-container resource planning, and scaling to hundreds of containers per host along with boot/overhead benchmarks.