One possibility, an upstart job could write to /dev/lxc in the container.
lxc-start would listen to the other end on the host, and update the container state to USERSPACE_RUNNING or somesuch. Then lxc-ls would show USERSPACE_RUNNING instead of RUNNING. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
