Restored LXCs Cannot Start After Re-Install

[CashewCaliphate]

I recently had to replace some drives, so I took the opportunity to do a fresh install of proxmox. I:

1. updated/upgraded all the packages on the proxmox host
2. backed up each container to a separate NFS storage share
3. Installed the new OS drives
4. Re-installed proxmox
5. Tried to restore the containers

This was all done within 12 hours, so I don't know how a package version (like apparmor) could make a difference.

Here's the container's log that failed to start:

    lxc-start 100 20180409082647.404 ERROR    lxc_container - lxccontainer.c:do_lxcapi_start:984 - Permission denied - Failed to make / rslave at startup
      lxc-start 100 20180409082647.404 ERROR    lxc_container - lxccontainer.c:wait_on_daemonized_start:751 - No such file or directory - Failed to receive the container state
      lxc-start 100 20180409082647.404 ERROR    lxc_start_ui - tools/lxc_start.c:main:371 - The container failed to start.
      lxc-start 100 20180409082647.404 ERROR    lxc_start_ui - tools/lxc_start.c:main:373 - To get more details, run the container in foreground mode.
      lxc-start 100 20180409082647.404 ERROR    lxc_start_ui - tools/lxc_start.c:main:375 - Additional information can be obtained by setting the --logfile and --logpriority options.
      lxc-start 100 20180409082745.189 ERROR    lxc_container - lxccontainer.c:do_lxcapi_start:984 - Permission denied - Failed to make / rslave at startup
      lxc-start 100 20180409082745.189 ERROR    lxc_container - lxccontainer.c:wait_on_daemonized_start:751 - No such file or directory - Failed to receive the container state
      lxc-start 100 20180409082745.189 ERROR    lxc_start_ui - tools/lxc_start.c:main:371 - The container failed to start.
      lxc-start 100 20180409082745.189 ERROR    lxc_start_ui - tools/lxc_start.c:main:373 - To get more details, run the container in foreground mode.
      lxc-start 100 20180409082745.189 ERROR    lxc_start_ui - tools/lxc_start.c:main:375 - Additional information can be obtained by setting the --logfile and --logpriority options.
      lxc-start 100 20180409083637.767 ERROR    lxc_container - lxccontainer.c:do_lxcapi_start:984 - Permission denied - Failed to make / rslave at startup
      lxc-start 100 20180409083637.767 ERROR    lxc_container - lxccontainer.c:wait_on_daemonized_start:751 - No such file or directory - Failed to receive the container state
      lxc-start 100 20180409083637.767 ERROR    lxc_start_ui - tools/lxc_start.c:main:371 - The container failed to start.
      lxc-start 100 20180409083637.767 ERROR    lxc_start_ui - tools/lxc_start.c:main:373 - To get more details, run the container in foreground mode.
      lxc-start 100 20180409083637.767 ERROR    lxc_start_ui - tools/lxc_start.c:main:375 - Additional information can be obtained by setting the --logfile and --logpriority options.

 

[dietmar]

I assume you run an old version. Please update your system.

 

[CashewCaliphate]

I assume you run an old version. Please update your system.

As I said in my original post, I:

1. updated/upgraded the proxmox host
2. backed-up each container
3. Re-installed the proxmox host (and updated/upgraded)
4. Tried to restore the container

All in the span of 12 hours.

So I don't know how an out of date system is even a possibility here. I'm on v5.1-46 :

root@pve:~# pveversion -v
proxmox-ve: 5.1-42 (running kernel: 4.13.16-1-pve)
pve-manager: 5.1-46 (running version: 5.1-46/ae8241d4)
pve-kernel-4.13: 5.1-43
pve-kernel-4.13.16-1-pve: 4.13.16-45
pve-kernel-4.13.13-2-pve: 4.13.13-33
corosync: 2.4.2-pve3
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.0-8
libpve-common-perl: 5.0-28
libpve-guest-common-perl: 2.0-14
libpve-http-server-perl: 2.0-8
libpve-storage-perl: 5.0-17
libqb0: 1.0.1-1
lvm2: 2.02.168-pve6
lxc-pve: 2.1.1-3
lxcfs: 2.0.8-2
novnc-pve: 0.6-4
proxmox-widget-toolkit: 1.0-11
pve-cluster: 5.0-20
pve-container: 2.0-19
pve-docs: 5.1-16
pve-firewall: 3.0-5
pve-firmware: 2.0-4
pve-ha-manager: 2.0-5
pve-i18n: 1.0-4
pve-libspice-server1: 0.12.8-3
pve-qemu-kvm: 2.9.1-9
pve-xtermjs: 1.0-2
qemu-server: 5.0-22
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.6-pve1~bpo9

 

[fabian]

you either need to activate a subscription or configure the pve-no-subscription repository to get upgrades to PVE packages.

 

[CashewCaliphate]

you either need to activate a subscription or configure the pve-no-subscription repository to get upgrades to PVE packages.

I did.

deb http://ftp.debian.org/debian stretch main contrib

# PVE pve-no-subscription repository provided by proxmox.com,
# NOT recommended for production use
deb http://download.proxmox.com/debian/pve stretch pve-no-subscription

# security updates
deb http://security.debian.org stretch/updates main contrib

 

[CashewCaliphate]

Out of desperation, I disabled the bind mount paths in the container config file and then it started right up. So it was missing the host-side path on a bind mount, it seems.