lxc container crashing

[LeifSec]

If have a LXC container within the latest Debian version (12) and updates.

It is running but after a few minutes it crashed and cannot be started again:

run_buffer: 321 Script exited with status 25
lxc_init: 846 Failed to run lxc.hook.pre-start for container "113"
__lxc_start: 2002 Failed to initialize container "113"
TASK ERROR: startup for container '113' failed

When trying to to a restore a got an error about missing Debian 12.1 image?

TASK ERROR: unable to restore CT 113 - unsupported debian version '12.1'

What is Debian 12.1?
At

http://download.proxmox.com/images/system/

there have never been any subversion of Linux distributions.

 

[cheiss]

there have never been any subversion of Linux distributions.

Sure there have been. Debian does this on a fairly regular schedule per release. See e.g. the release for Debian 12.1.

As for you problem - please provide the output of pveversion -v, this will help troubleshoot this further.

Edit:

run_buffer: 321 Script exited with status 25
lxc_init: 846 Failed to run lxc.hook.pre-start for container "113"
__lxc_start: 2002 Failed to initialize container "113"
TASK ERROR: startup for container '113' failed

Do you have a custom pre-start hook set? You can also try running pct start 113 -debug, this provides more verbose output.

 

[LeifSec]

Sure there have been. Debian does this on a fairly regular schedule per release. See e.g. the release for Debian 12.1.

Yes, for Debian there are X.Y releases - but there are no Proxmox Images with X.Y Y!=0: http://download.proxmox.com/images/system/.

As for you problem - please provide the output of pveversion -v, this will help troubleshoot this further.

proxmox-ve: 7.1-1 (running kernel: 5.13.19-2-pve)
pve-manager: 7.1-8 (running version: 7.1-8/5b267f33)
pve-kernel-helper: 7.1-6
pve-kernel-5.13: 7.1-5
pve-kernel-5.4: 6.4-11
pve-kernel-5.3: 6.1-6
pve-kernel-5.13.19-2-pve: 5.13.19-4
pve-kernel-5.4.157-1-pve: 5.4.157-1
pve-kernel-5.4.41-1-pve: 5.4.41-1
pve-kernel-5.3.18-3-pve: 5.3.18-3
pve-kernel-5.3.18-2-pve: 5.3.18-2
ceph-fuse: 14.2.21-1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: residual config
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.0
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-5
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-14
libpve-guest-common-perl: 4.0-3
libpve-http-server-perl: 4.0-4
libpve-storage-perl: 7.0-15
libqb0: 1.0.5-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.11-1
lxcfs: 4.0.11-pve1
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.1.2-1
proxmox-backup-file-restore: 2.1.2-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-4
pve-cluster: 7.1-2
pve-container: 4.1-3
pve-docs: 7.1-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.3-3
pve-ha-manager: 3.3-1
pve-i18n: 2.6-2
pve-qemu-kvm: 6.1.0-3
pve-xtermjs: 4.12.0-1
qemu-server: 7.1-4
smartmontools: 7.2-pve2
spiceterm: 3.2-2
swtpm: 0.7.0~rc1+2
vncterm: 1.7-1
zfsutils-linux: 2.1.1-pve3


That is quite old. And there is the critical bug that some VM have lost partitions and bootsectors after reboot which cannot be restored. But updating Proxmox (and the machine) requires a restart of Proxmox and within this all VMs ...

Edit:

Do you have a custom pre-start hook set? You can also try running pct start 113 -debug, this provides more verbose output.

Thanks a lot I will do this if the error appears next time. For the time being could restore on older backup and up to now there are no errors.

 

[cheiss]

Yes, for Debian there are X.Y releases - but there are no Proxmox Images with X.Y Y!=0: http://download.proxmox.com/images/system/.

So you mean our provided CT images? Still, for e.g. Debian, there is 11.3, 11.6 and 11.7. Not Debian 12.1 (yet), but still. So I'm not sure what you mean.

That is quite old.

Yes, that's really old. So consider upgrading as soon as possible.
Looking at the source, that's also the root of you problem. You version of the pve-container package only supports Debian up to 12, not including any minor releases after that.

If you cannot afford the downtime for upgrading & rebooting, one thing to consider (if possible) is (live-)migrating all VMs/CTs to another server, perform the upgrade and then migrate them back.