as @oguz suggested it seems that there is a problem with /sbin/init after the upgrade:
Code:
lxc-start 8022 20190403144525.650 NOTICE start - start.c:start:2075 - Exec'ing "/sbin/init"
lxc-start 8022 20190403144525.650 ERROR start - start.c:start:2078 - No such file or directory - Failed to exec "/sbin/init"
You could try to check the container's image and see why there is no /sbin/init:
* `pct mount $VMID`
* `ls /var/lib/lxc/$VMID/rootfs/sbin/init`
depending on whether it's an unprivileged container or privileged you can then try to either chroot inside it and try to install the missing packages, or to use `lxc-usernsexec` to change into the user-namespace for unprivileged containers and then chroot.
Probably it would be better to restore the original container from a backup and try to upgrade again - and make sure that init is upgraded properly (systemd is installed) before rebooting
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.