[lxc-users] Unsupervised containers

[Stewart Brodie]

<steve at linuxsuite.org> wrote:

> >
> > 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???

It's an embedded device with a requirement that, with the exception of init
as PID 1, all processes run inside containers (once the system has booted,
obviously)  Also, the only lxc-related files actually on the system (in
release builds) are lxc-start, lxc-monitord and liblxc.so*, so nobody's
going to be doing those things anyway

So whilst it's not the aim - it's just that I realise that would be an
inevitable consequence of removing the [lxc-monitor] process.

It would be possible to not use LXC at all, but it's so very convenient for
debug builds, which do also have lxc-console and lxc-stop (and consoles, and
interactive shells etc.)


-- 
Stewart Brodie
Senior Software Engineer
Espial UK