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?
No, I cannot reproduce this with the latest upstream kernel build 030900rc7- generic #201304171402)
(3.9.0-
What I did:
sudo lxc-create -t ubuntu- n r1 lxc/r0/ rootfs/ bin/
cat > exit0.c << EOF
#include <stdlib.h>
int main() {
exit(0);
}
EOF
make exit0
sudo cp exit0 /var/lib/
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?