After Upgrade lxc container did not start


Aug 23, 2017

after upgrading debian os and proxmox the lxc container did not start any longer. I read a many postings in the forum but nothing help me to run the lxc container. I have mount the container, cat debian_version is 8.11 inside. The OS of the host is 9.9.

Regards, Franz

Her some information i think can be helpful:

#pveversion -v
proxmox-ve: 5.4-1 (running kernel: 4.15.18-14-pve)
pve-manager: 5.4-5 (running version: 5.4-5/c6fdb264)
pve-kernel-4.15: 5.4-2
pve-kernel-4.15.18-14-pve: 4.15.18-38
pve-kernel-4.4.134-1-pve: 4.4.134-112
pve-kernel-4.4.44-1-pve: 4.4.44-84
corosync: 2.4.4-pve1
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.1-9
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-51
libpve-guest-common-perl: 2.0-20
libpve-http-server-perl: 2.0-13
libpve-storage-perl: 5.0-42
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-3
lxcfs: 3.0.3-pve1
novnc-pve: 1.0.0-3
proxmox-widget-toolkit: 1.0-26
pve-cluster: 5.0-37
pve-container: 2.0-37
pve-docs: 5.4-2
pve-edk2-firmware: 1.20190312-1
pve-firewall: 3.0-20
pve-firmware: 2.0-6
pve-ha-manager: 2.0-9
pve-i18n: 1.1-4
pve-libspice-server1: 0.14.1-2
pve-qemu-kvm: 3.0.1-2
pve-xtermjs: 3.12.0-1
qemu-server: 5.0-51
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3

#lxc-start -n 101 -l DEBUG -o /tmp/lxc-101.log
lxc-start 101 20190507181238.105 DEBUG conf - conf.c:run_buffer:326 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 101 lxc pre-start with output: closing file '/etc/inittab.tmp.12937' failed - No space left on device

lxc-start 101 20190507181238.106 DEBUG conf - conf.c:run_buffer:326 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 101 lxc pre-start with output: error in setup task PVE::LXC::Setup::pre_start_hook

lxc-start 101 20190507181238.112 ERROR conf - conf.c:run_buffer:335 - Script exited with status 1

lxc-start 101 20190507181238.112 ERROR start - start.c:lxc_init:861 - Failed to run lxc.hook.pre-start for container "101"

lxc-start 101 20190507181238.112 ERROR start - start.c:__lxc_start:1944 - Failed to initialize container "101"

lxc-start 101 20190507181238.411 DEBUG lxccontainer - lxccontainer.c:wait_on_daemonized_start:853 - First child 12922 exited

lxc-start 101 20190507181238.411 ERROR lxccontainer - lxccontainer.c:wait_on_daemonized_start:856 - No such file or directory - Failed to receive the container state

lxc-start 101 20190507181238.411 ERROR lxc_start - tools/lxc_start.c:main:330 - The container failed to start

lxc-start 101 20190507181238.411 ERROR lxc_start - tools/lxc_start.c:main:333 - To get more details, run the container in foreground mode

lxc-start 101 20190507181238.411 ERROR lxc_start - tools/lxc_start.c:main:336 - Additional information can be obtained by setting the --logfile and --logpriority options

# 101.conf
#--- Components ---
arch: amd64
cores: 1
hostname: nameserver-tm
memory: 512
net0: name=eth0,bridge=vmbr0,firewall=1,gw=,hwaddr=36:79:1E:4C:7B:C4,ip=,ip6=dhcp,type=veth
onboot: 1
ostype: debian
rootfs: local:101/vm-101-disk-1.raw,size=8G
swap: 512

dir: local
path /var/lib/vz
maxfiles 0
shared 0
content iso,images,backup,vztmpl,rootdir
Hi Dominik,
thanks for your answer, i solved it in the evening.
Increasing the size from 8G to 16G during restore let start the lxc container.
Kind regards,
pct restore 101 vzdump-lxc-101-2019_05_07-18_59_28.tar.lzo --storage local --rootfs local:16


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!