Ubuntu
lxc package

  1. Bug #1168526
  2. Comment #1

Comment 1 for bug 1168526

Revision history for this message
Serge Hallyn (serge-hallyn) wrote : Re: [Bug 1168526] [NEW] race condition causing lxc to not detect container init process exit

Quoting Pavel Bennett (<email address hidden>):
> Public bug reported:
>
> For the purpose of the repro, my lxc init process is node.js v0.11.0
> (built from source) with a single line:
>
> process.exit(0);

Thanks. This is a race condition we've seen before in lxc-execute.

Precisely which version of lxc were you using? The patch

0001-fix-race-with-fast-init

in ubuntu raring's recent lxc packages is meant to work around this,
but we don't have a clean fix yet.

> Notes:
> - I'm on Mint 14 Nadia with raring packages, if that helps.
> - In all cases, there is signal 17 (SIGCHLD) coming in to lxc-start, but it comes from a different pid and is ignored by lxc. Any idea what this could be? This process seems to have been cleaned up and no longer appears in ps aux.

That is the test for kernel support for reboot in a pidns. It's not
related to this.