No, I cannot reproduce this with the latest upstream kernel build
(3.9.0-030900rc7-generic #201304171402)
What I did:
sudo lxc-create -t ubuntu- n r1
cat > exit0.c << EOF
#include <stdlib.h>
int main() {
exit(0);
}
EOF
make exit0
sudo cp exit0 /var/lib/lxc/r0/rootfs/bin/
sudo lxc-start -n r1 -- /bin/exit0
Which only shows
lxc-start: No such file or directory -
stat(/proc/2620/root/dev/lxc/console)
but exits 0 correctly. If I do
sudo lxc-start -n r1 -l info -o outout -- /bin/exit0
then outout shows:
lxc-start 1366317913.390 INFO lxc_start - init has already
exited
Are you sure when you tested the newer kernel you weren't using a different
(unpatched) lxc?
** Changed in: lxc (Ubuntu)
Status: New => Incomplete
** Changed in: lxc (Ubuntu)
Assignee: Serge Hallyn (serge-hallyn) => (unassigned)
--
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
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
