Comment 17 for bug 1477720

I also get this when running sudo unity8-lxc-setup --rebuild:
> Starting the container
> Not able to connect to the network.

When trying to log into the unity8 lxc session afterwards, I get this in unity-system-compositor.log (probably expected?):
0
130
lxc_container: cgmanager.c: lxc_cgmanager_enter: 694 call to cgmanager_move_pid_abs_sync failed: invalid request
lxc_container: cgmanager.c: cgm_attach: 1324 Failed to enter group /lxc/unity8-lxc/init.scope
lxc_container: attach.c: lxc_attach: 831 error communicating with child process
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]

This is the output you requested:

$ sudo lxc-start -n unity8-lxc --logfile=/tmp/start_unity8-lxc.out --logpriority=DEBUG
lxc-start: lxc_start.c: main: 279 Container is already running.
$ sudo lxc-stop -n unity8-lxc # this takes quite long, maybe a minute
$ sudo lxc-start -n unity8-lxc --logfile=/tmp/start_unity8-lxc.out --logpriority=DEBUG
$

The file start_unity8-lxc.out is attached to this comment.