How to update LXC to new system release
- Thread starter epionier
- Start date
Disclaimer: guest OS updates are not part of any virtualization. You need to consult the guest os documentation.
For Debian specifically, those instruction will be available when Trixie is released. The last update from bullseye to bookworm was described in the Debian Handbook. This will be available when Trixie is released for the upgrade from bookworm to trixie.
For Debian specifically, those instruction will be available when Trixie is released. The last update from bullseye to bookworm was described in the Debian Handbook. This will be available when Trixie is released for the upgrade from bookworm to trixie.
Like LnxBil I would try the procedure from the official documentation from Debian. It's not finished yet (since Trixie is not released at the moment) but there is already a draft at https://www.debian.org/releases/trixie/release-notes/ Please note that that it's not finished at the moment.
Another option would be to rebuild the LXCs directly with the Trixie template and move your applications and data from the old container to the new one.
Another option would be to rebuild the LXCs directly with the Trixie template and move your applications and data from the old container to the new one.
Hello,
thanks for your statements. I am aware that Debian Trixie is not released yet. I just wanted to ask how tho update Debian LXCs when Trixie and PVE 9.0 (based on Trixie) are released.
As far as I understand you two right I just have to update my Debian LXCs then the way I would update a Debian Bookworm VM or a bare metal Debian Bookworm installation, in respect to the update instructions for Debian?
I was not sure about this because LXCs share kernel and some more with the host, that`s why I was asking.
thanks for your statements. I am aware that Debian Trixie is not released yet. I just wanted to ask how tho update Debian LXCs when Trixie and PVE 9.0 (based on Trixie) are released.
As far as I understand you two right I just have to update my Debian LXCs then the way I would update a Debian Bookworm VM or a bare metal Debian Bookworm installation, in respect to the update instructions for Debian?
I was not sure about this because LXCs share kernel and some more with the host, that`s why I was asking.
Yes, this should work.
At some point some containers won't work any more ( for example Ubuntu 16.04 and centos7 won't work with PVE 9 see https://pve.proxmox.com/pve-docs/chapter-pct.html#pct_cgroup_compat for more information
) due to incomatiblite changes in the host system but Bookworm to Trixie won't be a problem with PVE9. Future versions might be a different Story though.
Hello,
in the meantime I upgraded PVE Host to PVE version 9.0.
Everything is working and I left my LXCs on the installed Debian Bookworm base.
My question is: I have Debian sources on PVE (under v8 and v9) set to include the component: non-free-firmware for intel-microcode package.
I never included this in my LXCs so my question is. Does it makes sense or is it even recommendable to include non-free-firmware as component and install intel-microcode package within a LXC or is this already managed by PVE host with intel-microcode package installed?
in the meantime I upgraded PVE Host to PVE version 9.0.
Everything is working and I left my LXCs on the installed Debian Bookworm base.
My question is: I have Debian sources on PVE (under v8 and v9) set to include the component: non-free-firmware for intel-microcode package.
I never included this in my LXCs so my question is. Does it makes sense or is it even recommendable to include non-free-firmware as component and install intel-microcode package within a LXC or is this already managed by PVE host with intel-microcode package installed?