[lxc-users] Unsupervised containers

[steve at linuxsuite.org]

>
> Right now, there is one lxc-start process per container running (that has
> renamed itself in lxc 1.1.4 to [lxc-monitor]) to act as the interface to
> the
> container for various LXC tools.
>
> I'd like that process to exit once the container is up and running. I do
> not
> want to ever stop the container, connect to its console, freeze it or run
> any other LXC tools.  I just want the container to be started and left to
> run within the environment that lxc-start set up for it.
>
> So, is it possible to get it to exit cleanly but leave the containers to
> run
> unsupervised, and if so, how?

       Why would you ever want to remove all possibility of using lxc
tools to manage
a running container???

        If you are worried about containers taking over you sessions or
whatever..  Why not
just run them in screen

screen -dmS Container_1 lxc-start -n container_1

        -steve

>
> I did just try "kill -9" on the [lxc-monitor] process to see if the
> container could survive the loss, but whilst (busybox's) init is still
> running, the shells attached to tty devices inside the containers did not
> survive.
>
>
> --
> Stewart Brodie
> Senior Software Engineer
> Espial UK
> _______________________________________________
> lxc-users mailing list
> lxc-users at lists.linuxcontainers.org
> http://lists.linuxcontainers.org/listinfo/lxc-users