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

[Serge Hallyn]

Quoting Robie Basak (1266808 at bugs.launchpad.net):
> I want it generic because I want adt-virt-lxc to work with any container
> it is given, without having to tell the user to set up a special
> container with special stuff in this special way.
> 
> Other tools will want this too. I have a simple generic "trusty"
> container that I use to "start-ephemeral" (or "clone", I suppose)
> whatever testing I need. Multiple tools can end up using this (adt-virt-
> lxc and perhaps eventually a uvt-lxc). They need to agree on a common
> way to achieve this common task; I think the suitable place for this to
> go is lxc.

Each distro+release guest would need to be updated using its own init
system to inform us when the boot is complete, resulting in
container-specific changes to the rootfs which is something we want
to avoid.

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