I recently rebuilt my 4x Raspberry Pi 4 Incus cluster. I fully broke it while upgrading from Raspberry Pi OS "bookworm" to "trixie".
In the rebuild I upgraded to "trixie" when "bookworm" was freshly installed as the first thing I did and it went flawlessly.
I had a lot of troubles setting up the VLAN for the Incus nodes with NetworkManager and therefore went back to the "ifupdown" and "vlan" packages. I locked myself out multiple times and had to connect the SSDs to my laptop to edit the /etc/network/interfaces file that way to get back in. It was a hassle. I surely have to find out how to set up VLANs with NetworkManager. But now the nodes are on the right VLAN and I use macvlans for my containers in my cluster to use different VLANs.
I also had to install "resolvconf" to get DNS working with ifupdown.
The installation and setup of the Incus cluster itself was really easy and without problems. The documentation is really good.
Link:
https://linuxcontainers.org/incus/I just hope Debian (Raspberry Pi OS) won't drop the "ifupdown" and "vlan" packages in future releases, so I can upgrade to future releases easily and without hassle. Next time I'll wait until the new release is out, but I'm not really sure what broke the system. It just didn't recognize a root drive after reboot and there was no PARTUUID for it even when I plugged the drive to my laptop.
But however, now I have my own arm64 cloud to tinker with it again.
#RaspberryPi #Debian #Incus #LinuxContainers #NetworkManager