lxc configuration help - only network isolated?

Serge E. Hallyn serue at us.ibm.com
Fri Mar 27 06:08:59 PDT 2009

Quoting Daniel Lezcano (daniel.lezcano at free.fr):
> Chris R. Jones wrote:
> > I have a couple of basic configuration questions on linux containers.  I'm using lxc-0.6.1.
> >
> > I'm trying to configure a setup where I have two containers, where the only virtualized/isolated resources are network resources, but I can still do IPC between processes in the two containers.
> >
> > The lxc.conf man page indicates that, "by default, the pids, sysv ipc, and mount points are virtualized and isolated. "
> >
> > Is there a way in the configuration to specify that those resources should NOT be isolated?  I'd really like to have communication between two processes running in different containers using sysV IPC and signals.  The only thing I really want to be isolated are two different network namespaces.
> >
> > Is there a setting I use in the lxc.conf file to accomplish this?
> >
> >   
> I thought no one would be interested by less isolation :)
> I see you want to share the signals, that means no pid namespace, right ?
> The design of the lxc is build around the pid namespace, if you kill the 
> first process of the pid namespace, you kill all the process of the 
> container. That allows to implement the 'lxc-stop' command.
> So no pid namespace, no container :)

There has been discussion before about having a 'kill' or 'signal'
cgroup, analogous to the freezer, for sending signals to all tasks
in a cgroup.  We could push that, and have lxc-stop optionally use

If there were interest.

> > Up to now, I've been doing some prototyping using lxc-unshare -n, but that doesn't really create a container, correct?  That mostly accomplishes my goals, but I can't find a way to spawn new processes into that same namespace.  Is there a way, without defining a container?
> >   
> No, except writing a forker and launch it inside the container and have 
> a command outside to tell the forker to spawn a specific program. 
> Dietmar Maurer is working on such component to be integrated in lxc.
> > Any recommendations on how to properly configure a containers to allow IPC between processes in two different containers while still isolating the network resources?
> >   
> If you want to share the ipc to do some testing, you can hack the 
> lxc_start function in start.c and remove the ipc cloning flag.
> +clone_flags = CLONE_NEWPID|CLONE_NEWNS;
> I hope that helps.

I've heard this request in other places, especially about ipc, so maybe
it's a good idea to work such support into the config.  Maybe something


in lxc.conf, and mask keep_sharing out of clone_flags at lxc_start?


More information about the Containers mailing list