Debian 12 does not work after reboot

gusto · Aug 8, 2023

Code:

proxmox-ve: 7.3-1 (running kernel: 5.15.83-1-pve)
pve-manager: 7.3-4 (running version: 7.3-4/d69b70d4)
pve-kernel-5.15: 7.3-1
pve-kernel-helper: 7.3-1
pve-kernel-5.15.83-1-pve: 5.15.83-1
pve-kernel-5.15.74-1-pve: 5.15.74-1
ceph-fuse: 15.2.17-pve1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.3
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.3-1
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.3-1
libpve-guest-common-perl: 4.2-3
libpve-http-server-perl: 4.1-5
libpve-storage-perl: 7.3-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.0-3
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.3.2-1
proxmox-backup-file-restore: 2.3.2-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.5.3
pve-cluster: 7.3-1
pve-container: 4.4-2
pve-docs: 7.3-1
pve-edk2-firmware: 3.20220526-1
pve-firewall: 4.2-7
pve-firmware: 3.6-2
pve-ha-manager: 3.5.1
pve-i18n: 2.8-1
pve-qemu-kvm: 7.1.0-4
pve-xtermjs: 4.16.0-1
qemu-server: 7.3-2
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+2
vncterm: 1.7-1
zfsutils-linux: 2.1.7-pve2

I installed from the template debian-12-standard_12.0-1_amd64.tar.zst. Immediately after installation I reboot and Debian no longer works.

Code:

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

Code:

arch: amd64
cores: 2
features: keyctl=1,nesting=1
hostname: debian-12-test
memory: 1024
net0: name=eth0,bridge=vmbr2,gw=192.168.20.1,hwaddr=0A:F9:53:EA:6D:AA,ip=192.168.20.20/24,type=veth
ostype: debian
rootfs: local-zfs:subvol-114-disk-0,size=8G
swap: 512
unprivileged: 1

A month ago I installed 2x LXC with debian-12-standard_12.0-1_amd64.tar.zst and they work great.

gusto · Aug 8, 2023

I apologize, after installation rebooted without problems. A problem occurs even after the update

Code:

apt update  && apt upgrade -y

Code:

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

leesteken · Aug 8, 2023

gusto said:
I apologize, after installation rebooted without problems. A problem occurs even after the update

Code:

apt update && apt upgrade -y

Please never run apt upgrade (often a cause of problems on the forum) and instead use the GUI or apt dist-upgrade per the manual.

gusto · Aug 8, 2023

I tried, but same problem

Code:

apt update && apt dist-upgrade -y

Code:

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

However, I don't want to update proxmox, but LXC debian 12

Chris · Aug 8, 2023

gusto said:
I tried, but same problem

Code:

apt update && apt dist-upgrade -y

Code:

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

However, I don't want to update proxmox, but LXC debian 12

Did you run the above commands in the LXC or on the host? As @leesteken already stated, on PVE you will have to use apt dist-upgrade for correctly solving possible dependency conflicts during upgrade, inside the container the command you showed is okay.

Please post the output of pct start 114 --debug to see where the pre-start hook failes.

gusto · Aug 8, 2023

Code:

run_buffer: 321 Script exited with status 25
lxc_init: 847 Failed to run lxc.hook.pre-start for container "114"
__lxc_start: 2008 Failed to initialize container "114"
d 0 hostid 100000 range 65536
INFO     lsm - ../src/lxc/lsm/lsm.c:lsm_init_static:38 - Initialized LSM security driver AppArmor
INFO     conf - ../src/lxc/conf.c:run_script_argv:337 - Executing script "/usr/share/lxc/hooks/lxc-pve-prestart-hook" for container "114", config section "lxc"
DEBUG    conf - ../src/lxc/conf.c:run_buffer:310 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 114 lxc pre-start produced output: unsupported debian version '12.1'

ERROR    conf - ../src/lxc/conf.c:run_buffer:321 - Script exited with status 25
ERROR    start - ../src/lxc/start.c:lxc_init:847 - Failed to run lxc.hook.pre-start for container "114"
ERROR    start - ../src/lxc/start.c:__lxc_start:2008 - Failed to initialize container "114"
INFO     conf - ../src/lxc/conf.c:run_script_argv:337 - Executing script "/usr/share/lxcfs/lxc.reboot.hook" for container "114", config section "lxc"
startup for container '114' failed

Rares · Aug 8, 2023

Hi,

You need to update to latest Proxmox 7.4.

Rares

Chris · Aug 8, 2023

Seems like your pve-container package is not new enough, you need at least version 5.0.2 for Debian 12.1 support. Please upgrade your host.

gusto · Aug 8, 2023

Well thank you. I thought so. However, I have to wait another week.
Alternatively, can I do a dist-upgrade without rebooting PVE?

I plan to install Proxmox 8 soon

Rares · Aug 8, 2023

You can always run Debian12 inside a VM instead of CT.

fiona · Aug 8, 2023

Hi,

Chris said:
Seems like your pve-container package is not new enough, you need at least version 5.0.2 for Debian 12.1 support. Please upgrade your host.

or pve-container>=4.4-5 in Proxmox VE 7. But if you want to upgrade to Proxmox VE 8 (needs to be done sooner or later anyways), see: https://pve.proxmox.com/wiki/Upgrade_from_7_to_8

gusto · Aug 8, 2023

I don't like upgrading proxmox. A clean installation is better.

Retro1982 · Aug 8, 2023

Hi,

i ran into the same problem and i did a little dirty hack to allow the lxc to start:

i edited /usr/share/perl5/PVE/LXC/Setup/Debian.pm

and changed

if !($version >= 4 && $version <= 12);

to

Code:

if !($version >= 4 && $version <= 13);

since bookworm reports itself as 12.1

Just a quick and dirty hack, maybe it helps to get bookworm up and running without upgrading

Best regards,
Martin

tom · Aug 8, 2023

You just need to update your Proxmox VE to latest 7.4 (or to 8)

(Not applying updates - including security fixes - is a bad idea)

Search

Search

Debian 12 does not work after reboot

gusto

Well-Known Member

gusto

Well-Known Member

leesteken

Distinguished Member

gusto

Well-Known Member

Chris

Proxmox Staff Member

gusto

Well-Known Member

Rares

Well-Known Member

Chris

Proxmox Staff Member

gusto

Well-Known Member

Rares

Well-Known Member

fiona

Proxmox Staff Member

gusto

Well-Known Member

Retro1982

New Member

tom

Proxmox Staff Member