[SOLVED] Is the Unmanaged OS Type for LXC Not Supported on PVE9 Anymore?

[Taylan]

Hello everyone,


After upgrading to Proxmox VE 9, I’m experiencing some issues with my LXC containers, specifically with OpenWRT. My OpenWRT LXC container no longer starts, and I’m unable to create a new one with the same "unmanaged" OS type as I did on PVE 8.


Has anyone else encountered this issue? Is the unmanaged OS type for LXC no longer supported in PVE9, or is there something I’m missing in the configuration?


Here are the error messages I’m getting when trying to start the container:

root@Proxmox:~# pct start 111 --debug
run_buffer: 571 Script exited with status 255
lxc_init: 845 Failed to run lxc.hook.pre-start for container "111"
__lxc_start: 2046 Failed to initialize container "111"
0 hostid 100000 range 65536
INFO     lsm - ../src/lxc/lsm/lsm.c:lsm_init_static:38 - Initialized LSM security driver AppArmor
INFO     utils - ../src/lxc/utils.c:run_script_argv:587 - Executing script "/usr/share/lxc/hooks/lxc-pve-prestart-hook" for container "111", config section "lxc"
DEBUG    utils - ../src/lxc/utils.c:run_buffer:560 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 111 lxc pre-start produced output: Can't locate object method "check_systemd_nesting" via package "PVE::LXC::Setup::Unmanaged" at /usr/share/perl5/PVE/LXC/Setup.pm line 304.

ERROR    utils - ../src/lxc/utils.c:run_buffer:571 - Script exited with status 255
ERROR    start - ../src/lxc/start.c:lxc_init:845 - Failed to run lxc.hook.pre-start for container "111"
ERROR    start - ../src/lxc/start.c:__lxc_start:2046 - Failed to initialize container "111"
INFO     utils - ../src/lxc/utils.c:run_script_argv:587 - Executing script "/usr/share/lxc/hooks/lxc-pve-poststop-hook" for container "111", config section "lxc"
startup for container '111' failed
root@Proxmox:~# lxc-start --foreground -lDEBUG 111
lxc-start: 111: ../src/lxc/utils.c: run_buffer: 571 Script exited with status 255
lxc-start: 111: ../src/lxc/start.c: lxc_init: 845 Failed to run lxc.hook.pre-start for container "111"
lxc-start: 111: ../src/lxc/start.c: __lxc_start: 2046 Failed to initialize container "111"
lxc-start: 111: ../src/lxc/tools/lxc_start.c: lxc_start_main: 307 The container failed to start
lxc-start: 111: ../src/lxc/tools/lxc_start.c: lxc_start_main: 312 Additional information can be obtained by setting the --logfile and --logpriority options

And the error messages I'm getting when trying to create a new container with the following command:

root@Proxmox:~# pct create 119 /var/lib/vz/template/cache/openwrt-23.05.tar.xz --arch amd64 --hostname test --rootfs Containers:0.12 --memory 128 --cores 2 --ostype unmanaged --
unprivileged 1 --onboot 1 --searchdomain 9.9.9.9 --nameserver 1.1.1.1 --swap 0 --net0 name=eth0,bridge=vmbr0v30,firewall=1,ip=dhcp,type=veth --net1 name=eth1,bridge=vmbr1,firewa
ll=1,type=veth --tags servarr
extracting archive '/var/lib/vz/template/cache/openwrt-23.05.tar.xz'
Total bytes read: 14295040 (14MiB, 93MiB/s)
unable to create CT 119 - Can't locate object method "check_systemd_nesting" via package "PVE::LXC::Setup::Unmanaged" at /usr/share/perl5/PVE/LXC/Setup.pm line 304.

Any help or guidance would be greatly appreciated!

Here is the common error message I'm getting:

Can't locate object method "check_systemd_nesting" via package "PVE::LXC::Setup::Unmanaged" at /usr/share/perl5/PVE/LXC/Setup.pm line 304.

Thanks in advance!

 

[mfederanko]

Reported here https://bugzilla.proxmox.com/show_bug.cgi?id=7270

 

[Taylan]

Thank you, the patch works indeed.

 

[Arcticpollen]

Thank you, the patch works indeed.

Hi, I've got the same issue trying to rebuild an OpenWRT container but despite looking at the bug report and some other posts on the same issue, I can't work out how to apply the patch to my Proxmox 9.1.5 host. I could do with getting OpenWRT running again as I have a few other containers that sit behind it.
Could you let me have an idea of how to manually apply the patch?

 

[Taylan]

I’m on mobile, so only can say, I’ve used the patch command on the diff on the mailing list.

 

[Arcticpollen]

Thanks @Taylan - I wasn't sure which were the correct files to apply the dfferences to so in the end, I've just downgraded pve-container to 6.0.18 which has got me back up and running with OpenWRT for now.

Seems there are other issues with pve-container 6.1.0 to do with container mount points so I assume that a fixed version will be along at some point.

 

[Arcticpollen]

I've just updated pve-container to the freshly released 6.1.1 version which has resolved my issue for my OpenWRT container allowing me to restart it correctly.