> Each distro+release guest would need to be updated using its own init system to inform us when the boot is complete
LXC could provide a default implementation (like the above "wait until runlevel switches to 2 and then notify the caller"), and then templates could optionally provide a more refined version of that. I see nothing wrong with that, given that the notion of "when is the container safe to work with" seems quite universal? I see nothing wrong with putting that knowledge into the templates; that's pretty much exactly where it belongs to IMHO. -- 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
