[SOLVED] The Container failed to start.

vzfanatic

Active Member
Jul 22, 2008
67
0
26
i have a new debian 9 image downloaded from the templates repository provided by pm4. I created a container and everything was normal until a reboot of the container then it would not start. pve details are:

proxmox-ve: 4.4-76 (running kernel: 4.4.35-1-pve)
pve-manager: 4.4-1 (running version: 4.4-1/eb2d6f1e)
pve-kernel-4.4.35-1-pve: 4.4.35-76
lvm2: 2.02.116-pve3
corosync-pve: 2.4.0-1
libqb0: 1.0-1
pve-cluster: 4.0-48
qemu-server: 4.0-101
pve-firmware: 1.1-10
libpve-common-perl: 4.0-83
libpve-access-control: 4.0-19
libpve-storage-perl: 4.0-70
pve-libspice-server1: 0.12.8-1
vncterm: 1.2-1
pve-docs: 4.4-1
pve-qemu-kvm: 2.7.0-9
pve-container: 1.0-88
pve-firewall: 2.0-33
pve-ha-manager: 1.0-38
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u3
lxc-pve: 2.0.6-2
lxcfs: 2.0.5-pve1
criu: 1.6.0-1
novnc-pve: 0.5-8
smartmontools: 6.5+svn4324-1~pve80
zfsutils: 0.6.5.8-pve13~bpo80


the error is

lxc-start: tools/lxc_start.c: main: 365 The container failed to start.
lxc-start: tools/lxc_start.c: main: 367 To get more details, run the container i
n foreground mode.
lxc-start: tools/lxc_start.c: main: 369 Additional information can be obtained b
y setting the --logfile and --logpriority options.

the log file says:
lxc-start 20171025003525.240 INFO lxc_start_ui - tools/lxc_start.c:main:275 - using rcfile /var/lib/lxc/109/c
onfig
lxc-start 20171025003525.240 WARN lxc_confile - confile.c:config_pivotdir:1910 - lxc.pivotdir is ignored. It
will soon become an error.
lxc-start 20171025003525.241 INFO lxc_lsm - lsm/lsm.c:lsm_init:48 - LSM security driver AppArmor
lxc-start 20171025003525.241 INFO lxc_seccomp - seccomp.c:parse_config_v2:402 - processing: .reject_force_umo
unt # comment this to allow umount -f; not recommended.
lxc-start 20171025003525.241 INFO lxc_seccomp - seccomp.c:parse_config_v2:567 - Adding native rule for reject
_force_umount action 0.
lxc-start 20171025003525.241 INFO lxc_seccomp - seccomp.c:do_resolve_add_rule:251 - Setting Seccomp rule to r
eject force umounts.
lxc-start 20171025003525.241 INFO lxc_seccomp - seccomp.c:parse_config_v2:570 - Adding compat rule for reject
_force_umount action 0.
lxc-start 20171025003525.241 INFO lxc_seccomp - seccomp.c:do_resolve_add_rule:251 - Setting Seccomp rule to r
eject force umounts.
lxc-start 20171025003525.241 INFO lxc_seccomp - seccomp.c:parse_config_v2:402 - processing: .[all].
lxc-start 20171025003525.241 INFO lxc_seccomp - seccomp.c:parse_config_v2:402 - processing: .kexec_load errno
1.
lxc-start 20171025003525.241 INFO lxc_seccomp - seccomp.c:parse_config_v2:567 - Adding native rule for kexec_
load action 327681.
lxc-start 20171025003525.241 INFO lxc_seccomp - seccomp.c:parse_config_v2:570 - Adding compat rule for kexec_
load action 327681.
lxc-start 20171025003525.241 INFO lxc_seccomp - seccomp.c:parse_config_v2:402 - processing: .open_by_handle_a
t errno 1.
lxc-start 20171025003525.241 INFO lxc_seccomp - seccomp.c:parse_config_v2:567 - Adding native rule for open_b
y_handle_at action 327681.
lxc-start 20171025003525.241 INFO lxc_seccomp - seccomp.c:parse_config_v2:570 - Adding compat rule for open_b
y_handle_at action 327681.
lxc-start 20171025003525.241 INFO lxc_seccomp - seccomp.c:parse_config_v2:402 - processing: .init_module errn
o 1.
lxc-start 20171025003525.241 INFO lxc_seccomp - seccomp.c:parse_config_v2:567 - Adding native rule for init_m
odule action 327681.
lxc-start 20171025003525.241 INFO lxc_seccomp - seccomp.c:parse_config_v2:570 - Adding compat rule for init_m
odule action 327681.
lxc-start 20171025003525.241 INFO lxc_seccomp - seccomp.c:parse_config_v2:402 - processing: .finit_module err
no 1.
lxc-start 20171025003525.241 INFO lxc_seccomp - seccomp.c:parse_config_v2:567 - Adding native rule for finit_
module action 327681.
lxc-start 20171025003525.241 WARN lxc_seccomp - seccomp.c:do_resolve_add_rule:270 - Seccomp: got negative for
syscall: -10085: finit_module.
lxc-start 20171025003525.241 WARN lxc_seccomp - seccomp.c:do_resolve_add_rule:271 - This syscall will NOT be
blacklisted.
lxc-start 20171025003525.241 INFO lxc_seccomp - seccomp.c:parse_config_v2:570 - Adding compat rule for finit_
module action 327681.
lxc-start 20171025003525.241 WARN lxc_seccomp - seccomp.c:do_resolve_add_rule:270 - Seccomp: got negative for
syscall: -10085: finit_module.
lxc-start 20171025003525.241 WARN lxc_seccomp - seccomp.c:do_resolve_add_rule:271 - This syscall will NOT be
blacklisted.
lxc-start 20171025003525.241 INFO lxc_seccomp - seccomp.c:parse_config_v2:402 - processing: .delete_module er
rno 1.
lxc-start 20171025003525.241 INFO lxc_seccomp - seccomp.c:parse_config_v2:567 - Adding native rule for delete
_module action 327681.
lxc-start 20171025003525.241 INFO lxc_seccomp - seccomp.c:parse_config_v2:570 - Adding compat rule for delete
_module action 327681.
lxc-start 20171025003525.241 INFO lxc_seccomp - seccomp.c:parse_config_v2:580 - Merging in the compat Seccomp
ctx into the main one.
lxc-start 20171025003525.242 INFO lxc_conf - conf.c:run_script_argv:367 - Executing script '/usr/share/lxc/ho
oks/lxc-pve-prestart-hook' for container '109', config section 'lxc'
lxc-start 20171025003525.865 ERROR lxc_conf - conf.c:run_buffer:347 - Script exited with status 25
lxc-start 20171025003525.865 ERROR lxc_start - start.c:lxc_init:450 - Failed to run lxc.hook.pre-start for con
tainer "109".
lxc-start 20171025003525.865 ERROR lxc_start - start.c:__lxc_start:1313 - Failed to initialize container "109"
.
lxc-start 20171025003525.865 ERROR lxc_start_ui - tools/lxc_start.c:main:365 - The container failed to start.
lxc-start 20171025003525.865 ERROR lxc_start_ui - tools/lxc_start.c:main:369 - Additional information can be o
btained by setting the --logfile and --logpriority options.

does any one know what's wrong?
 
I also did this:

lxc-start --name=109 --foreground
unsupported debian version '9.2'

how is the version 'unsupported' when it was downloaded from within pm4 from the container repository? o_O

whats the solution for this?
 
this was fixed a while ago, please upgrade your pve installation to the latest 4.4
 
how?
# apt-get -y dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
 
ok, i see.. the iso installer seems to not have included the repo in the sources.
 
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!