[SOLVED] Can't start container after updating

[PlOrAdmin]

Hi, running PVE 6.0-4

I had a CT running pihole and updated it(apt update, apt upgrade) connecting with lxc-attach --name ID

After I typed reboot it dropped back to host shell.

I cannot start container. I get this error. Not sure what I am looking for when I run the commands to troubleshoot.

The CT wasn't important so I tried to reproduce the problem. Created new container, update within and reboot. Same issue.
Is this a bug in PVE6 or am I doing something that shouldn't be needing doing?

I posted this question on reddit and another user experienced same issue. https://old.reddit.com/r/Proxmox/comments/d1yy4c/cant_start_container_after_updating_it/

Thanks.

 

[Chris]

Hi,
please start the container in foreground mode and provide the debug logs. For this you have to run lxc-start -n CTID -F -l DEBUG -o /tmp/lxc-CTID.log with CTID being the ID of your container.

 

[PlOrAdmin]

Hi,

I don't understand what foreground mode is. Here is the log file from another fresh CT install.

Thanks.

 

[Chris]

Hi,

I don't understand what foreground mode is. Here is the log file from another fresh CT install.

Thanks.

There is an error stating that Debian 10.1 is not supported, which is not true for up to date packages. Please update all the packages on your PVE host to the latest version and try again.

 

[PlOrAdmin]

Hi,

My host(v 6.0-4) was updated already. I installed deb9 CT also as a test. It works after updates/reboot but 10 does not. I even tried DHCP in as a grasping of straws to see if my configuration of static IP was the problem lol.

The version pveam available shows for 10 is: debian-10.0-standard_10.0-1_amd64.tar.gz

I'm going to run my CTs in 9 for now. I hope this helps you folks diagnose what's going on. If you want me to test anything further I'll do my best to help.

Thanks.

 

[Rowe]

Hello. I would like to add that I am having the exact same problem as well.
The host is fully updated. Whenever I run apt update && apt upgrade on any container, and reboot it afterwards, it cannot start again. Just like OP.

Here is a log file from a fresh container, not that I think it will be any different from OPs, but anyways.

 

[Chris]

Please provide the output of `pveversion -v`

 

[Raito00]

I have the same problem!

 

[Rowe]

Please provide the output of `pveversion -v`

I could see on reddit that OP figured it out for himself. He edited the file /etc/apt/sources.list.d/pve-community.list, and changed stretch to buster. That took him past version 6.0-4, which is where I am still stuck.
I do not know if that file is only used if you have a subscription, but in either case, mine did already say buster, so I still have a problem.

Here is the output from 'pveversion -v'

root@proxmox01:~# pveversion -v
proxmox-ve: 6.0-2 (running kernel: 5.0.15-1-pve)
pve-manager: 6.0-4 (running version: 6.0-4/2a719255)
pve-kernel-5.0: 6.0-5
pve-kernel-helper: 6.0-5
pve-kernel-5.0.15-1-pve: 5.0.15-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.2-pve2
criu: 3.11-3
glusterfs-client: 5.5-3
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.10-pve1
libpve-access-control: 6.0-2
libpve-apiclient-perl: 3.0-2
libpve-common-perl: 6.0-2
libpve-guest-common-perl: 3.0-1
libpve-http-server-perl: 3.0-2
libpve-storage-perl: 6.0-5
libqb0: 1.0.5-1
lvm2: 2.03.02-pve3
lxc-pve: 3.1.0-61
lxcfs: 3.0.3-pve60
novnc-pve: 1.0.0-60
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.0-5
pve-cluster: 6.0-4
pve-container: 3.0-3
pve-docs: 6.0-4
pve-edk2-firmware: 2.20190614-1
pve-firewall: 4.0-5
pve-firmware: 3.0-2
pve-ha-manager: 3.0-2
pve-i18n: 2.0-2
pve-qemu-kvm: 4.0.0-3
pve-xtermjs: 3.13.2-1
qemu-server: 6.0-5
smartmontools: 7.0-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.1-pve1

 

[Chris]

I could see on reddit that OP figured it out for himself. He edited the file /etc/apt/sources.list.d/pve-community.list, and changed stretch to buster. That took him past version 6.0-4, which is where I am still stuck.
I do not know if that file is only used if you have a subscription, but in either case, mine did already say buster, so I still have a problem.

Here is the output from 'pveversion -v'

root@proxmox01:~# pveversion -v
proxmox-ve: 6.0-2 (running kernel: 5.0.15-1-pve)
pve-manager: 6.0-4 (running version: 6.0-4/2a719255)
pve-kernel-5.0: 6.0-5
pve-kernel-helper: 6.0-5
pve-kernel-5.0.15-1-pve: 5.0.15-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.2-pve2
criu: 3.11-3
glusterfs-client: 5.5-3
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.10-pve1
libpve-access-control: 6.0-2
libpve-apiclient-perl: 3.0-2
libpve-common-perl: 6.0-2
libpve-guest-common-perl: 3.0-1
libpve-http-server-perl: 3.0-2
libpve-storage-perl: 6.0-5
libqb0: 1.0.5-1
lvm2: 2.03.02-pve3
lxc-pve: 3.1.0-61
lxcfs: 3.0.3-pve60
novnc-pve: 1.0.0-60
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.0-5
pve-cluster: 6.0-4
pve-container: 3.0-3
pve-docs: 6.0-4
pve-edk2-firmware: 2.20190614-1
pve-firewall: 4.0-5
pve-firmware: 3.0-2
pve-ha-manager: 3.0-2
pve-i18n: 2.0-2
pve-qemu-kvm: 4.0.0-3
pve-xtermjs: 3.13.2-1
qemu-server: 6.0-5
smartmontools: 7.0-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.1-pve1

Please provide the output of

cat /etc/apt/sources.list /etc/apt/sources.list.d/*

 

[Rowe]

Please provide the output of

cat /etc/apt/sources.list /etc/apt/sources.list.d/*

Thank you for replying, but I created another thread, and figured it out
https://forum.proxmox.com/threads/debian-10-lxc-container-wont-start-after-apt-upgrade.58376/