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

[Robie Basak]

On Tue, Jan 28, 2014 at 02:06:30PM -0000, Serge Hallyn wrote:
> 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.

I understand your reasoning, but requiring tools that consume LXC to
make these container-specific changes to the rootfs is worse; especially
when there's one general concept that will need duplicated
implementations across all consumers. You're just forcing the problem
downstream, and the problem is exacerbated there.

If you insist on not doing it this way, how about "contrib" style
scripts, provided in the lxc package, which understands different init
systems and arranges the wait mechanism? This would be a
"idempotently-modify-this-container-to-add-boot-wait" command, with another
"boot-wait-on-the-container-i-modified" command. Then at least the code
will be in one place, and all consumers will use the same mechanism.
A consumer would have to run the container modification script in
between clone and container start (I assume this is possible).

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