[Lxc-users] LXC Debian Wheezy Template

[Guido Jäkel]

Dear list,

in a private communication i recommend Daniel to use a more recent kernel than the "conservative" V3.2 shipped with Wheezy. He wrote me that this have solved the "shutdown/reboot" issue.

I had have a similar problem and Serge explained me, that on a more recent kernel (>=3.4?) lxc-start may rely on a namespace-aware shutdown system call (and don't need to drop CAP_SYS_BOOT for that). Before, it need to watch the containers utemp file and this will become unavailable if it is "overmounted" by a tmpfs by the containers init framwork.


greetings

Guido

On 2013-07-31 12:01, Danijel Vargek, Continum wrote:
> Hi everybody,
> is there a way to use Debian-Wheezy containers in a clean,
> working way on lxc?
> 
> My current setup involves a Debian-Wheezy Host with several Wheezy containers.
> As stated on the Debian wiki (wiki.debian.org/LXC), the original template ships
> with several problems (mainly missing ttys for console login and other stuff).
> 
> We set up our containers with the template recommended on this mailinglist. 
> Installation worked pretty fine, but there are some problems according to the
> init scripts:
> 
> 1. Stopping/Restarting containers via /etc/init.d/lxc fails with a timeout:
> ####
> [....] Stopping Linux Containers: test.xxx.com
> telinit: timeout opening/writing control channel /run/initctl
> ####
> 
> 2. Shutdown/Reboot inside a container stops all processes except of init, so the
> container finally does not shutdown or reboot.
> We can see the still active init process for the container via lxc-ps
> ####
> CONTAINER    PID TTY          TIME CMD
> test.xxx.com  4352 ?        00:00:05 init
> ####
> The only way to finally stop a container is via lxc-stop
> 
> Did anyone experience a similiar problem, or is there an existing workaround for 
> this?
> 
> Regards,
> Danijel
>