> I see one problem with that. Directly calling lxc-stop outside of the
> container, or half in the container will cause upstart to restart it,
> which isn't quite what we want.
I explicitly did not add the 'respawn' stanza to the .conf file, I just
mentioned it as a possible and valid use case. T
Public bug reported:
This change proposes that upstart takes care of running and managing lxc
container instances instead of having them run as daemons.
This has some advantages:
- lxc containers can benefit from upstart supervision, eg. respawn can be
easily enabled, and parallel job execution
