All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Chris R. Jones" <chris-SqNQQPNds68nxqbYAscKCQ@public.gmane.org>
To: containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org
Subject: lxc configuration help - only network isolated?
Date: Thu, 26 Mar 2009 15:45:41 -0700	[thread overview]
Message-ID: <20090326224541.GA25769@versecorp.net> (raw)

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?

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?

Any recommendations on how to properly configure a containers to allow IPC between processes in two different containers while still isolating the network resources?

Thanks,
Chris

             reply	other threads:[~2009-03-26 22:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-26 22:45 Chris R. Jones [this message]
     [not found] ` <20090326224541.GA25769-SqNQQPNds68nxqbYAscKCQ@public.gmane.org>
2009-03-27  8:46   ` lxc configuration help - only network isolated? Daniel Lezcano
     [not found]     ` <49CC9262.40302-GANU6spQydw@public.gmane.org>
2009-03-27 13:08       ` Serge E. Hallyn
     [not found]         ` <20090327130859.GA9643-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-03-28  3:27           ` Matt Helsley
  -- strict thread matches above, loose matches on Subject: below --
2009-04-08 22:38 Elwin Stelzer Eliazer
     [not found] ` <638f07d70904081538x6a132466xd0607466487e106e-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-04-08 22:44   ` Serge E. Hallyn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090326224541.GA25769@versecorp.net \
    --to=chris-sqnqqpnds68nxqbyasckcq@public.gmane.org \
    --cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.