When I try upgrade my cluster it wont, still looking at 6.9 - best suggestions a I get are remove Incus and reinstall nothing I want to do on production servers.
What is the most painless way to do this?
When I try upgrade my cluster it wont, still looking at 6.9 - best suggestions a I get are remove Incus and reinstall nothing I want to do on production servers.
What is the most painless way to do this?
This what Grok says
The rsync method isn’t working because the file locations and libraries for deb-packaged Incus on Ubuntu 20.04 are more scattered than expected (some are in /usr/lib/x86_64-linux-gnu/, some in other places, and dependencies vary).
Adding the “correct” old Zabbly repository for focal won’t help anymore — as of mid-2025, the Incus maintainer (Stéphane Graber / Zabbly) completely removed all Ubuntu 20.04 (focal) packages from https://pkgs.zabbly.com because the distro is end-of-life. That’s why you always get 404s. There is no archive or hidden repo to add back.
This is what literally everyone running Incus on Ubuntu 20.04 does now. Snap Incus is identical in functionality and clusters perfectly with deb Incus as long as the version number matches — and snap always gives the latest version instantly.
On every node (do the old ones one-by-one; the cluster stays up):
Bash
# Remove deb version if present
sudo apt remove --purge incus incus-client incus-base lxd* -y 2>/dev/null || true
# Install snap Incus (latest version everywhere)
sudo snap install incus
# Add yourself to the admin group (optional but recommended)
sudo adduser $USER incus-admin
newgrp incus-admin # or just log out/in
After this, incus version will show the exact same ~6.20 on every node. Generate a new join token and add Q2 (or any new servers) — done forever, no more version drama.
If you really want to keep the old deb version temporarily:
Good to see that the AIs are still hallucinating just as much…
There is obviously no such thing as an incus snap package, even less so an official one ![]()
It also recommends using apt remove --purge which would typically wipe all data during package removal, so yeah, quality response there.
Yeah, I decide not follow its advice. I think best solution is to update all machines to 24.04 but can’t do that remote so going have to wait for colo visit. I believe it did get part right about new versions no longer supporting 20.04