Hi, plymouth running in the container prevents me from using the container at all, it kills my X instead:
I created a 11.10 container with the following lxc-create command on freshly installed 11.10: sudo lxc-create -n ubuntu1 -f ./ubuntu1-template.conf -t ubuntu -- --release=oneiric --path=/data/lxc/ubuntu1 here ubuntu1-template.conf contains this: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ lxc.network.type = veth lxc.network.flags = up lxc.network.link = virbr0 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ (virbr0 being the bridge created by libvirt) Now when I later start the container with "sudo lxc-start -n ubuntu1" (after sudo lxc-create -n ubuntu1 -f /data/lxc/ubuntu1/config), then there is no output but after a couple of seconds, my X session is killed placing me in the login manager. When I do lxc-ps -n ubuntu1, I see only plymouthd is running except for init. After disabling plymouth in the container by "mv /etc/init/plymouth.conf /etc/init/plymouth.conf.gone", I was able to start the container successfully. So maybe plymouth should really be disabled in the container. Cheers - Michael -- 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/925513 Title: plymouth should not run in container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/925513/+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