[Bug 1266808] Re: No mechanism to wait until a started container is ready and has finished booting

[Stéphane Graber]

The listening end would be lxc-start, the other end would be whatever is
appropriate.

In Ubuntu this could be an upstart job, on Debian a sysvinit script, ...
There wouldn't be a need for a persistent connection, the socket would just be there to send messages from the container to the host, so anything could use netcat to do something like: echo "state ready" | nc -U /dev/lxc

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1266808

Title:
  No mechanism to wait until a started container is ready and has
  finished booting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1266808/+subscriptions