All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serge-A9i7LUbDfNHQT0dZR+AlfA@public.gmane.org>
To: Richard Weinberger
	<richard.weinberger-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Linux Containers
	<containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>,
	"systemd-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org"
	<systemd-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>,
	LXC development mailing-list
	<lxc-devel-cunTk1MwBs9qMoObBWhMNEqPaTDuhLve2LY78lusg7I@public.gmane.org>
Subject: Re: How to use cgroups within containers?
Date: Sat, 18 Oct 2014 05:50:12 +0200	[thread overview]
Message-ID: <20141018035012.GA16300@mail.hallyn.com> (raw)
In-Reply-To: <CAFLxGvxKP2wkGOqW=mz7Sv=+yJXiY-1Hz-4kKfR8mYVEWPOj6Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Quoting Richard Weinberger (richard.weinberger-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org):
> ...fixing LXC devel mailinglist... :-\
> 
> On Fri, Oct 17, 2014 at 11:35 PM, Richard Weinberger
> <richard.weinberger-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> > Dear systemd and container folks,
> >
> > at Plumbers the question raised how to provide cgroups to a systemd that lives
> > in a container (with user namespaces).
> > Due to the GDL train strikes I had to leave very soon and had no chance to
> > talk to you in person.
> >
> > Was a solution proposed?
> > All I want to know is how to provide cgroups in a sane and secure way
> > to systemd. :-)

My takeaway from the discussion was that there was general agreement that
the cgroup namespaces patches posted by Aditya Kali would solve the
problem.

-serge

  parent reply	other threads:[~2014-10-18  3:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-17 21:35 How to use cgroups within containers? Richard Weinberger
     [not found] ` <CAFLxGvxKP2wkGOqW=mz7Sv=+yJXiY-1Hz-4kKfR8mYVEWPOj6Q@mail.gmail.com>
     [not found]   ` <CAFLxGvxKP2wkGOqW=mz7Sv=+yJXiY-1Hz-4kKfR8mYVEWPOj6Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-10-17 21:52     ` [systemd-devel] " Cameron Norman
2014-10-18  3:50     ` Serge E. Hallyn [this message]
     [not found] ` <CAFLxGvxzmfhLZPsmsFG9qdB0oDf9ayvNaWNNOXqcAkW3yATffg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-10-17 21:37   ` Richard Weinberger
2014-10-20 16:24   ` [systemd-devel] " Lennart Poettering
     [not found] ` <20141020162445.GA4008@gardel-login>
2014-10-20 16:49   ` Richard Weinberger
     [not found]   ` <54453D06.9020101@nod.at>
     [not found]     ` <54453D06.9020101-/L3Ra7n9ekc@public.gmane.org>
2014-10-20 16:51       ` Lennart Poettering
2014-10-20 16:55         ` Richard Weinberger
     [not found]           ` <54453E6F.6000202-/L3Ra7n9ekc@public.gmane.org>
2014-10-20 17:04             ` Lennart Poettering
     [not found]           ` <20141020170442.GA4271@gardel-login>
2014-10-20 17:16             ` Richard Weinberger
     [not found]               ` <54454355.90605-/L3Ra7n9ekc@public.gmane.org>
2014-10-20 17:27                 ` Lennart Poettering
2014-10-20 17:33                   ` Richard Weinberger

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=20141018035012.GA16300@mail.hallyn.com \
    --to=serge-a9i7lubdfnhqt0dzr+alfa@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=lxc-devel-cunTk1MwBs9qMoObBWhMNEqPaTDuhLve2LY78lusg7I@public.gmane.org \
    --cc=richard.weinberger-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=systemd-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@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.