Setup and running LXC container is really easy, but sometimes it is unclear why the LXC container could not start. Most of the time, there is a generic error, which says nothing for the real reason:
root@srv ~ # lxc-start -n test-lxc lxc-start: test-lxc: lxccontainer.c: wait_on_daemonized_start: 867 Received container state "ABORTING" instead of "RUNNING" lxc-start: test-lxc: tools/lxc_start.c: main: 306 The container failed to start lxc-start: test-lxc: tools/lxc_start.c: main: 309 To get more details, run the container in foreground mode lxc-start: test-lxc: tools/lxc_start.c: main: 311 Additional information can be obtained by setting the --logfile and --logpriority options
No specific reason why the LXC container test-lxc can not be started and the lxc-start command failed. There is just an offer to use the logging options and here is how the administrator of the box may do it by including the following lxc-start options:
-l DEBUG –logfile=test-lxc.log –logpriority=9
Here is a real-world example of an old kernel trying to run LXC 4.0
Keep on reading!