After years of running LXC and LXD, this is a somewhat recurring topic
which has no good answers, all distros do it differently and the
definition of ready differs even user to user.
So from LXC's point of view, it's best to stay away from this and
instead have users actually check for what they care, be it a web
service being ready, cloud-init indicating it's done running or whatever
else and just use LXC's tools and API to run those checks.
** Changed in: lxc (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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
Status in lxc package in Ubuntu:
Won't Fix
Bug description:
If I script a container start, I also want to script a wait until the
container has finished booting. Otherwise I start using the container,
write to /tmp, and then /tmp gets cleaned. I'm sure there are more
race conditions, too.
It would be nice if lxc-wait could be extended to support some
mechanism to detect this, or if not lxc-wait then some other generic
mechanism that templates could then support.
cloud-init writes a boot-finished flag which could be used on
systems/templates that use cloud-init.
Also see cloud-init bug 1258113.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1266808/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
