[SOLVED] Debian 10 LXC Container won't start after 'apt upgrade'

limone

Member
Aug 1, 2017
68
0
6
25
Hi,
I have an interesting phenomenon with my proxmox (6.0-4). If I create a container with the official Debian 10 image (debian-10.0-standard_10.0-1_amd64.tar.gz) it will work until I update the packages. After that the container will not survive a reboot:

Code:
28 packages can be upgraded. Run 'apt list --upgradable' to see them.
N: Repository 'http://ftp.debian.org/debian buster InRelease' changed its 'Version' value from '10.0' to '10.1'
Reading package lists... Done
Building dependency tree... Done
Calculating upgrade... Done
The following packages will be upgraded:
  base-files bzip2 e2fsprogs gpgv libbz2-1.0 libcom-err2 libcryptsetup12 libext2fs2
  libldap-2.4-2 libldap-common libncurses6 libncursesw6 libnghttp2-14
  libnss-systemd libpam-systemd libss2 libsystemd0 libtinfo6 libudev1 ncurses-base
  ncurses-bin ncurses-term python3-reportbug reportbug systemd systemd-sysv tzdata
  udev
28 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 10.3 MB of archives.
After this operation, 16.4 kB of additional disk space will be used.
Get:1 http://security.debian.org buster/updates/main amd64 libnghttp2-14 amd64 1.36.0-2+deb10u1 [85.0 kB]
Get:2 http://ftp.debian.org/debian buster/main amd64 base-files amd64 10.3+deb10u1 [69.7 kB]
Get:3 http://ftp.debian.org/debian buster/main amd64 ncurses-bin amd64 6.1+20181013-2+deb10u1 [406 kB]
Get:4 http://ftp.debian.org/debian buster/main amd64 ncurses-base all 6.1+20181013-2+deb10u1 [258 kB]
Get:5 http://ftp.debian.org/debian buster/main amd64 libnss-systemd amd64 241-7~deb10u1 [204 kB]
Get:6 http://ftp.debian.org/debian buster/main amd64 libsystemd0 amd64 241-7~deb10u1 [330 kB]
Get:7 http://ftp.debian.org/debian buster/main amd64 libpam-systemd amd64 241-7~deb10u1 [208 kB]
Get:8 http://ftp.debian.org/debian buster/main amd64 systemd amd64 241-7~deb10u1 [3495 kB]
Get:9 http://ftp.debian.org/debian buster/main amd64 udev amd64 241-7~deb10u1 [1276 kB]
Get:10 http://ftp.debian.org/debian buster/main amd64 libudev1 amd64 241-7~deb10u1 [149 kB]
Get:11 http://ftp.debian.org/debian buster/main amd64 systemd-sysv amd64 241-7~deb10u1 [98.8 kB]
Get:12 http://ftp.debian.org/debian buster/main amd64 libcryptsetup12 amd64 2:2.1.0-5+deb10u2 [193 kB]
Get:13 http://ftp.debian.org/debian buster/main amd64 libext2fs2 amd64 1.44.5-1+deb10u1 [220 kB]
Get:14 http://ftp.debian.org/debian buster/main amd64 e2fsprogs amd64 1.44.5-1+deb10u1 [575 kB]
Get:15 http://ftp.debian.org/debian buster/main amd64 bzip2 amd64 1.0.6-9.2~deb10u1 [48.4 kB]
Get:16 http://ftp.debian.org/debian buster/main amd64 libbz2-1.0 amd64 1.0.6-9.2~deb10u1 [45.3 kB]
Get:17 http://ftp.debian.org/debian buster/main amd64 gpgv amd64 2.2.12-1+deb10u1 [584 kB]
Get:18 http://ftp.debian.org/debian buster/main amd64 libncurses6 amd64 6.1+20181013-2+deb10u1 [102 kB]
Get:19 http://ftp.debian.org/debian buster/main amd64 libtinfo6 amd64 6.1+20181013-2+deb10u1 [325 kB]
Get:20 http://ftp.debian.org/debian buster/main amd64 libncursesw6 amd64 6.1+20181013-2+deb10u1 [132 kB]
Get:21 http://ftp.debian.org/debian buster/main amd64 tzdata all 2019b-0+deb10u1 [260 kB]
Get:22 http://ftp.debian.org/debian buster/main amd64 ncurses-term all 6.1+20181013-2+deb10u1 [490 kB]
Get:23 http://ftp.debian.org/debian buster/main amd64 reportbug all 7.5.3~deb10u1 [128 kB]
Get:24 http://ftp.debian.org/debian buster/main amd64 python3-reportbug all 7.5.3~deb10u1 [134 kB]
Get:25 http://ftp.debian.org/debian buster/main amd64 libcom-err2 amd64 1.44.5-1+deb10u1 [68.4 kB]
Get:26 http://ftp.debian.org/debian buster/main amd64 libldap-common all 2.4.47+dfsg-3+deb10u1 [89.6 kB]
Get:27 http://ftp.debian.org/debian buster/main amd64 libldap-2.4-2 amd64 2.4.47+dfsg-3+deb10u1 [225 kB]
Get:28 http://ftp.debian.org/debian buster/main amd64 libss2 amd64 1.44.5-1+deb10u1 [72.8 kB]
Code:
root@pve-lab:~# pct start 100

Job for pve-container@100.service failed because the control process exited with error code.
See "systemctl status pve-container@100.service" and "journalctl -xe" for details.
command 'systemctl start pve-container@100' failed: exit code 1
Code:
Sep 14 13:45:59 pve-lab systemd[1]: Starting PVE LXC Container: 100...
Sep 14 13:46:00 pve-lab lxc-start[6494]: lxc-start: 100: lxccontainer.c: wait_on_daemonized_start: 856 No such file or directory - Failed to receive the container state
Sep 14 13:46:01 pve-lab lxc-start[6494]: lxc-start: 100: tools/lxc_start.c: main: 330 The container failed to start
Sep 14 13:46:01 pve-lab lxc-start[6494]: lxc-start: 100: tools/lxc_start.c: main: 333 To get more details, run the container in foreground mode
Sep 14 13:46:01 pve-lab lxc-start[6494]: lxc-start: 100: tools/lxc_start.c: main: 336 Additional information can be obtained by setting the --logfile and --logpriority options
Sep 14 13:46:00 pve-lab systemd[1]: pve-container@100.service: Control process exited, code=exited, status=1/FAILURE
Sep 14 13:46:00 pve-lab systemd[1]: pve-container@100.service: Failed with result 'exit-code'.
Sep 14 13:46:00 pve-lab systemd[1]: Failed to start PVE LXC Container: 100.
Any idea why? :(
 

sg90

Member
Sep 21, 2018
131
18
18
29
From another thread with the same issue it was noted their has been some fixes in updates on Promox for this.

You should update to the current 6.0-7 and try again
 

PlOrAdmin

New Member
May 22, 2019
29
3
3
45
> You should update to the current 6.0-7 and try again

Hi, how can I do this? The GUI update doesn't show any updates. I also tried apt update && apt -y dist-upgrade in PVE root shell and it didn't show anything either.

Thanks.
 

LnxBil

Well-Known Member
Feb 21, 2015
4,217
408
83
Germany
> You should update to the current 6.0-7 and try again

Hi, how can I do this? The GUI update doesn't show any updates. I also tried apt update && apt -y dist-upgrade in PVE root shell and it didn't show anything either.

Thanks.
There there is no update in the repository you configured.
 

Tiago Barrionuevo

New Member
Sep 16, 2019
1
0
1
51
From another thread with the same issue it was noted their has been some fixes in updates on Promox for this.

You should update to the current 6.0-7 and try again
I use the 5.4 version and can't upgrade to 6 right now!
I'll try to update 5.4 with last packages later and see it solves the problem.

By now I found out the problem is base-files package update.
After update base-files package I edited "/etc/debian_version" and change its value from "10.1" to "10.0" and the system restarted without problems!
 

oguz

Proxmox Staff Member
Staff member
Nov 19, 2018
760
80
28

Stoiko Ivanov

Proxmox Staff Member
Staff member
May 2, 2018
2,030
205
63

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE 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 your own in 60 seconds.

Buy now!