lxc containers won't start after upgrade

lethargos

Well-Known Member
Jun 10, 2017
134
6
58
74
Hi,
After doing an upgrade today of libapparmor among other packages, my containers stopped working.
May 07 12:33:41 svorng10 lxc-start[2929]: lxc-start: 503: lxccontainer.c: wait_on_daemonized_start: 751 No such file or directory - Failed to receive the container state
May 07 12:33:41 svorng10 lxc-start[2929]: lxc-start: 503: tools/lxc_start.c: main: 371 The container failed to start.
May 07 12:33:41 svorng10 lxc-start[2929]: lxc-start: 503: tools/lxc_start.c: main: 373 To get more details, run the container in foreground mode.
May 07 12:33:41 svorng10 lxc-start[2929]: lxc-start: 503: tools/lxc_start.c: main: 375 Additional information can be obtained by setting the --logfile and --logpriority options.
(i can never identify the code formatting on this forum, it's simply impossible. No idea why you've gone to such lengths to HIDE it)


lxc-start -F -l DEBUG -L /root/503.log -n 503
lxc-start: 503: lxccontainer.c: do_lxcapi_start: 984 Permission denied - Failed to make / rslave at startup
lxc-start: 503: tools/lxc_start.c: main: 371 The container failed to start.
lxc-start: 503: tools/lxc_start.c: main: 375 Additional information can be obtained by setting the --logfile and --logpriority options.


503.log says:
lxc-start 503 20180507094513.936 INFO lxc_start_ui - tools/lxc_start.c:main:280 - using rcfile /var/lib/lxc/503/config
lxc-start 503 20180507094513.936 TRACE lxc_commands - commands.c:lxc_cmd:290 - command get_init_pid tries to connect command socket
lxc-start 503 20180507094513.936 TRACE lxc_commands - commands.c:lxc_cmd:295 - command get_init_pid failed to connect command socket: Connection refused
lxc-start 503 20180507094513.936 TRACE lxc_commands - commands.c:lxc_cmd:290 - command get_cgroup tries to connect command socket
lxc-start 503 20180507094513.936 TRACE lxc_commands - commands.c:lxc_cmd:295 - command get_cgroup failed to connect command socket: Connection refused
lxc-start 503 20180507094513.936 TRACE lxc_commands - commands.c:do_lxc_cmd_get_cgroup_path:439 - command get_cgroup failed for container "503": Connection refused.
lxc-start 503 20180507094513.936 TRACE lxc_commands - commands.c:lxc_cmd:290 - command get_state tries to connect command socket
lxc-start 503 20180507094513.936 TRACE lxc_commands - commands.c:lxc_cmd:295 - command get_state failed to connect command socket: Connection refused
lxc-start 503 20180507094513.936 TRACE lxc_start - start.c:lxc_init_handler:592 - unix domain socket 4 for command server is ready
lxc-start 503 20180507094513.936 ERROR lxc_container - lxccontainer.c:do_lxcapi_start:984 - Permission denied - Failed to make / rslave at startup
lxc-start 503 20180507094513.936 ERROR lxc_start_ui - tools/lxc_start.c:main:371 - The container failed to start.
lxc-start 503 20180507094513.936 ERROR lxc_start_ui - tools/lxc_start.c:main:375 - Additional information can be obtained by setting the --logfile and --logpriority options.



I'm using Proxmox 5.1-41, pve-container 2.0-18, apparmor 2.11.0-3+deb9u2

Thanks
 
Last edited:
Please update the pve packages, make sure lxc-pve is >= 2.1.1-3
 

About

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!