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

[Martin Pitt]

In this millenium the concept of "finished booting" becomes more and
more blurry anyway. We still have something like that with sysvinit if
you do an rc2.d/S99_something, but with upstart/systemd/udev rules this
already isn't accurate.

To use the least common denominator we could have a late rc2.d sysvinit
script do that, to notify callers that the container has booted
sufficiently to have a working file system etc. This already won't
guarantee us that the network is up (NetworkManager!) but any particular
condition (wait for network, wait for ssh, etc.) that the lxc-wait
caller expects can then be done using commands that you send to the
container. So I think the initial "wait until its safe to send files to
the container and run commands in it" provides a nice baseline which
shouldn't be Debian specific if we use the runlevel/sysv approach from
above. (Please keep in mind that this isn't just for autopkgtests, but
that you can easily have e. g. a Fedora container on Ubuntu).

-- 
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