From: Bennet Gallein <me@bennetgallein.de>
To: pve-user@pve.proxmox.com
Subject: [PVE-User] LXC Container not bootable in 7.2-15
Date: Sat, 19 Nov 2022 12:24:44 +0100 [thread overview]
Message-ID: <a179c82c-f4a4-bac0-5f6d-ca0afe2acf75@bennetgallein.de> (raw)
Hello together,
I just upgraded to 7.2-15 in the test-repository and all of my
Containers does not want to start.
Here is the output when i manually run "pct start 103 -debug=1":
root@pm-02:~# pct start 103 --debug=1
run_buffer: 321 Script exited with status 2
lxc_init: 847 Failed to run lxc.hook.pre-start for container "103"
__lxc_start: 2008 Failed to initialize container "103"
id 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 "103", config section "lxc"
DEBUG conf - ../src/lxc/conf.c:run_buffer:310 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 103 lxc pre-start produced output: objdump on /usr/lib/systemd/systemd failed: open3: exec of objdump -p /var/lib/lxc/103/rootfs/usr/lib/systemd/systemd failed: No such file or directory at /usr/share/perl5/PVE/Tools.pm line 455.
ERROR conf - ../src/lxc/conf.c:run_buffer:321 - Script exited with status 2
ERROR start - ../src/lxc/start.c:lxc_init:847 - Failed to run lxc.hook.pre-start for container "103"
ERROR start - ../src/lxc/start.c:__lxc_start:2008 - Failed to initialize container "103"
startup for container '103' failed
These containers don't have anything special.
Any help is appreciated.
Cheers
--
Bennet Gallein
https://bennetgallein.de
Elbinger Str. 18, 21339 Lueneburg, Germany
USt-IdNr.: DE320525917
next reply other threads:[~2022-11-19 11:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-19 11:24 Bennet Gallein [this message]
2022-11-19 11:26 ` Bennet Gallein
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a179c82c-f4a4-bac0-5f6d-ca0afe2acf75@bennetgallein.de \
--to=me@bennetgallein.de \
--cc=pve-user@pve.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox