I've downgraded systemd to 225-1ubuntu9.1 from wily/proposed. Kernel is still linux-image-4.5.0-040500rc4-generic and lxc is 1.1.5-0ubuntu0.15.10.3 from wily-updates.
Unfortunately, when I now start the lxc container, I seem to hit a different bug. I get:
lxc-start 1455870309.289 INFO lxc_conf - conf.c:setup_tty:1080 - 4 tty(s) has been setup
lxc-start 1455870309.289 INFO lxc_conf - conf.c:setup_personality:1473 - set personality to '0x0'
lxc-start 1455870309.289 DEBUG lxc_conf - conf.c:setup_caps:2279 - drop capability 'mac_admin' (33)
lxc-start 1455870309.289 DEBUG lxc_conf - conf.c:setup_caps:2279 - drop capability 'mac_override' (32)
lxc-start 1455870309.289 DEBUG lxc_conf - conf.c:setup_caps:2279 - drop capability 'sys_time' (25)
lxc-start 1455870309.289 DEBUG lxc_conf - conf.c:setup_caps:2279 - drop capability 'sys_module' (16)
lxc-start 1455870309.289 DEBUG lxc_conf - conf.c:setup_caps:2288 - capabilities have been setup
lxc-start 1455870309.289 NOTICE lxc_conf - conf.c:lxc_setup:4026 - 'aansluitform-deploy' is setup.
lxc-start 1455870309.289 WARN lxc_apparmor - lsm/apparmor.c:apparmor_process_label_set:167 - Incomplete AppArmor support in your kernel
lxc-start 1455870309.289 ERROR lxc_apparmor - lsm/apparmor.c:apparmor_process_label_set:169 - If you really want to start this container, set
lxc-start 1455870309.289 ERROR lxc_apparmor - lsm/apparmor.c:apparmor_process_label_set:170 - lxc.aa_allow_incomplete = 1
lxc-start 1455870309.289 ERROR lxc_apparmor - lsm/apparmor.c:apparmor_process_label_set:171 - in your container configuration file
lxc-start 1455870309.289 ERROR lxc_sync - sync.c:__sync_wait:51 - invalid sequence number 1. expected 4
lxc-start 1455870309.289 ERROR lxc_start - start.c:__lxc_start:1213 - failed to spawn 'aansluitform-deploy'
lxc-start 1455870309.290 ERROR lxc_cgmanager - cgmanager.c:cgm_remove_cgroup:523 - call to cgmanager_remove_sync failed: invalid request
lxc-start 1455870309.290 ERROR lxc_cgmanager - cgmanager.c:cgm_remove_cgroup:525 - Error removing all:lxc/aansluitform-deploy-8
lxc-start 1455870309.317 WARN lxc_commands - commands.c:lxc_cmd_rsp_recv:172 - command get_init_pid failed to receive response
lxc-start 1455870309.317 WARN lxc_cgmanager - cgmanager.c:cgm_get:994 - do_cgm_get exited with error
lxc-start 1455870314.321 ERROR lxc_start_ui - lxc_start.c:main:344 - The container failed to start.
lxc-start: lxc_start.c: main: 344 The container failed to start.
lxc-start 1455870314.321 ERROR lxc_start_ui - lxc_start.c:main:346 - To get more details, run the container in foreground mode.
lxc-start: lxc_start.c: main: 346 To get more details, run the container in foreground mode.
lxc-start 1455870314.321 ERROR lxc_start_ui - lxc_start.c:main:348 - Additional information can be obtained by setting the --logfile and --logpriority options.
lxc-start: lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options.
When adding the suggested apparmor parameter to the config file, the apparmor error disappear, but the cgmanager errors are identical (but different than before)...
Any ideas?
I've downgraded systemd to 225-1ubuntu9.1 from wily/proposed. Kernel is still linux-image- 4.5.0-040500rc4 -generic and lxc is 1.1.5-0ubuntu0. 15.10.3 from wily-updates.
Unfortunately, when I now start the lxc container, I seem to hit a different bug. I get:
lxc-start 1455870309.289 INFO lxc_conf - conf.c: setup_tty: 1080 - 4 tty(s) has been setup setup_personali ty:1473 - set personality to '0x0' setup_caps: 2279 - drop capability 'mac_admin' (33) setup_caps: 2279 - drop capability 'mac_override' (32) setup_caps: 2279 - drop capability 'sys_time' (25) setup_caps: 2279 - drop capability 'sys_module' (16) setup_caps: 2288 - capabilities have been setup lxc_setup: 4026 - 'aansluitform- deploy' is setup. c:apparmor_ process_ label_set: 167 - Incomplete AppArmor support in your kernel c:apparmor_ process_ label_set: 169 - If you really want to start this container, set c:apparmor_ process_ label_set: 170 - lxc.aa_ allow_incomplet e = 1 c:apparmor_ process_ label_set: 171 - in your container configuration file __sync_ wait:51 - invalid sequence number 1. expected 4 __lxc_start: 1213 - failed to spawn 'aansluitform- deploy' c:cgm_remove_ cgroup: 523 - call to cgmanager_ remove_ sync failed: invalid request c:cgm_remove_ cgroup: 525 - Error removing all:lxc/ aansluitform- deploy- 8 c:lxc_cmd_ rsp_recv: 172 - command get_init_pid failed to receive response c:cgm_get: 994 - do_cgm_get exited with error c:main: 344 - The container failed to start. c:main: 346 - To get more details, run the container in foreground mode. c:main: 348 - Additional information can be obtained by setting the --logfile and --logpriority options.
lxc-start 1455870309.289 INFO lxc_conf - conf.c:
lxc-start 1455870309.289 DEBUG lxc_conf - conf.c:
lxc-start 1455870309.289 DEBUG lxc_conf - conf.c:
lxc-start 1455870309.289 DEBUG lxc_conf - conf.c:
lxc-start 1455870309.289 DEBUG lxc_conf - conf.c:
lxc-start 1455870309.289 DEBUG lxc_conf - conf.c:
lxc-start 1455870309.289 NOTICE lxc_conf - conf.c:
lxc-start 1455870309.289 WARN lxc_apparmor - lsm/apparmor.
lxc-start 1455870309.289 ERROR lxc_apparmor - lsm/apparmor.
lxc-start 1455870309.289 ERROR lxc_apparmor - lsm/apparmor.
lxc-start 1455870309.289 ERROR lxc_apparmor - lsm/apparmor.
lxc-start 1455870309.289 ERROR lxc_sync - sync.c:
lxc-start 1455870309.289 ERROR lxc_start - start.c:
lxc-start 1455870309.290 ERROR lxc_cgmanager - cgmanager.
lxc-start 1455870309.290 ERROR lxc_cgmanager - cgmanager.
lxc-start 1455870309.317 WARN lxc_commands - commands.
lxc-start 1455870309.317 WARN lxc_cgmanager - cgmanager.
lxc-start 1455870314.321 ERROR lxc_start_ui - lxc_start.
lxc-start: lxc_start.c: main: 344 The container failed to start.
lxc-start 1455870314.321 ERROR lxc_start_ui - lxc_start.
lxc-start: lxc_start.c: main: 346 To get more details, run the container in foreground mode.
lxc-start 1455870314.321 ERROR lxc_start_ui - lxc_start.
lxc-start: lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options.
When adding the suggested apparmor parameter to the config file, the apparmor error disappear, but the cgmanager errors are identical (but different than before)...
Any ideas?