[Bug 1168526] Re: race condition causing lxc to not detect container init process exit
Serge Hallyn
1168526 at bugs.launchpad.net
Fri Jun 21 19:20:06 UTC 2013
Quoting Pavel Bennett (launchpad at pavelbennett.com):
> I can't try Saucy right now, but the repro instructions with kernel
> versions are in the original post and in #2.
>
> We've tried node v0.11.2 as well on Raring and got the repro.
>
> Repro summary:
>
> Install any of the above kernels, such as the one with the Raring installer, then install lxc from apt.
> Get node v0.11.0 - v0.11.2 or try any other recent version if that's easier, just not below v0.10.
Sorry, this is where I'm unclear. Can you please point me to exactly
where you grab the source (or which package you are using)?
> lxc init process is "/usr/local/bin/node /boot/mio-init.js" which
contains only "process.exit(0);" and try running 100 of these, whether
in parallel or one at a time. Continue until lxc-start doesn't exit. Run
"ps faux" and look for zombie children of lxc-start.
thanks,
-serge
--
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/1168526
Title:
race condition causing lxc to not detect container init process exit
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1168526/+subscriptions
More information about the Ubuntu-server-bugs
mailing list