I also have this problem.
I build a container with debootstrap --variant minbase
I then confirmed the files in rootfs.lucid/dev were present and had the appropriate permissions.
I wrote a basic config defining the network, container name, root , etc
The container starts but does not mount proc sys dev/shm or dev/pts
If I chroot in and manually mount then restart the container, still no joy.
The container itself outputs
# lxc-start -n lucid
mountall: Could not connect to Plymouth
I attempted to use the upstart script I use in my karmic openvz VPS, but it did not help.
I also have this problem.
I build a container with debootstrap --variant minbase
I then confirmed the files in rootfs.lucid/dev were present and had the appropriate permissions.
I wrote a basic config defining the network, container name, root , etc
The container starts but does not mount proc sys dev/shm or dev/pts
If I chroot in and manually mount then restart the container, still no joy.
The container itself outputs
# lxc-start -n lucid
mountall: Could not connect to Plymouth
I attempted to use the upstart script I use in my karmic openvz VPS, but it did not help.