Proxmox 8.4.12 and Debian 13.1 LXC containers

[reinob]

Today debian trixie got an update 13.0 → 13.1.
My updated LXC containers stopped starting.

I had to edit /usr/share/perl5/PVE/LXC/Setup/Debian.pm, which had

die "unsupported debian version '$version'\n" if !($version >= 4 && $version <= 13);

to

die "unsupported debian version '$version'\n" if !($version >= 4 && $version <= 14);

So just in case other people are wondering what's up.

In general, I would prefer if Proxmox didn't allow container startup to "die" unless there is a very good/real reason..

 

[tsv0]

same thing applies to PVE 9.x

 

[leesteken]

It also happened to all PBS 4.x running in a container (which is a supported way to run PBS), which just got upgraded to 13.1. It should probably be < 14 though.

 

[O.Haupt]

Hello,
I am new to this forum and would like to contribute something right away.

Changing the value from $version <= 13 to $version <= 14 also solved the problem for me.

Thanks to reinob.

 

[Steffenprox]

Applied the fix also but, restore a Backup did still not working in proxmox 8.4.12 with Non production-ready repository enabled!

 

[O.Haupt]

Applied the fix also but, restore a Backup did still not working in proxmox 8.4.12 with Non production-ready repository enabled!

Hi,
did you restart Proxmox after making the change?

I ran systemctl restart pvedaemon pve-cluster pveproxy

 

[Steffenprox]

Hi,
did you restart Proxmox after making the change?

I ran systemctl restart pvedaemon pve-cluster pveproxy

This did help to restoring backups. Thank you!

 

[reinob]

There is a new version of pve-container (5.3.1) where the test is for debian version < 15, which should be OK for a while

from changelog

setup: debian: increase upper supported version limit from <= 13 to < 15
to ensure all points releases of Debian 13 and future Debian 14 get
accepted.

 

[t.lamprecht]

There is a new version of pve-container (5.3.1) where the test is for debian version < 15, which should be OK for a while

Exactly, and more importantly it changes the check from <= to < to avoid that X.0 passes the check but X.1 does not.
See my post at https://forum.proxmox.com/threads/d...-fails-to-create-start-fix.171435/post-798952 for a bit more context.

 

[reinob]

Thanks, and also for fixing the issue so quickly, even for non subscribers!

 

[leesteken]

Fixes for paid subscriptions always come later, not sooner ;-)