This was discussed a few times upstream.
The suggested implementation is to have lxc-start create and bind /dev/lxc in
the container as a standard unix socket.
A simple text based protocol would then be built on top of this including
support for switching to a new "ready" state.
The idea is that an init script in the container could then do: echo
"state ready" | nc -U /dev/lxc
However this never got implemented and isn't on the roadmap for now, so if you
need this feature, patches implementing the suggestion above are definitely
welcome.
** Changed in: lxc (Ubuntu)
Status: New => Triaged
--
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
