the ct can't start
# lxc-start -n 119 -F -lDEBUG -o lxc-119.log --logpriority TRACE
lxc-start: 119: lxccontainer.c: do_lxcapi_start: 984 Permission denied - Failed to make / rslave at startup
lxc-start: 119: tools/lxc_start.c: main: 371 The container failed to start.
lxc-start: 119: tools/lxc_start.c: main: 375 Additional information can be obtained by setting the --logfile and --logpriority options.
Code:
lxc-start 119 20180721131225.356 INFO lxc_start_ui - tools/lxc_start.c:main:280 - using rcfile /var/lib/lxc/119/config
lxc-start 119 20180721131225.356 TRACE lxc_commands - commands.c:lxc_cmd:290 - command get_init_pid tries to connect command socket
lxc-start 119 20180721131225.356 TRACE lxc_commands - commands.c:lxc_cmd:295 - command get_init_pid failed to connect command socket: Connection refused
lxc-start 119 20180721131225.356 TRACE lxc_commands - commands.c:lxc_cmd:290 - command get_cgroup tries to connect command socket
lxc-start 119 20180721131225.356 TRACE lxc_commands - commands.c:lxc_cmd:295 - command get_cgroup failed to connect command socket: Connection refused
lxc-start 119 20180721131225.356 TRACE lxc_commands - commands.c:do_lxc_cmd_get_cgroup_path:439 - command get_cgroup failed for container "119": Connection refused.
lxc-start 119 20180721131225.356 TRACE lxc_commands - commands.c:lxc_cmd:290 - command get_state tries to connect command socket
lxc-start 119 20180721131225.356 TRACE lxc_commands - commands.c:lxc_cmd:295 - command get_state failed to connect command socket: Connection refused
lxc-start 119 20180721131225.356 TRACE lxc_start - start.c:lxc_init_handler:592 - unix domain socket 4 for command server is ready
lxc-start 119 20180721131225.356 ERROR lxc_container - lxccontainer.c:do_lxcapi_start:984 - Permission denied - Failed to make / rslave at startup
lxc-start 119 20180721131225.356 ERROR lxc_start_ui - tools/lxc_start.c:main:371 - The container failed to start.
lxc-start 119 20180721131225.356 ERROR lxc_start_ui - tools/lxc_start.c:main:375 - Additional information can be obtained by setting the --logfile and --logpriority options.
# pveversion -v
proxmox-ve: 5.1-32 (running kernel: 4.13.13-2-pve)
pve-manager: 5.1-41 (running version: 5.1-41/0b958203)
pve-kernel-4.13.13-2-pve: 4.13.13-32
libpve-http-server-perl: 2.0-8
lvm2: 2.02.168-pve6
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-19
qemu-server: 5.0-18
pve-firmware: 2.0-3
libpve-common-perl: 5.0-25
libpve-guest-common-perl: 2.0-14
libpve-access-control: 5.0-7
libpve-storage-perl: 5.0-17
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-3
pve-docs: 5.1-12
pve-qemu-kvm: 2.9.1-5
pve-container: 2.0-18
pve-firewall: 3.0-5
pve-ha-manager: 2.0-4
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.1.1-2
lxcfs: 2.0.8-1
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.7.3-pve1~bpo9
openvswitch-switch: 2.6.2~pre+git20161223-3