Linux Container Development
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: "Chris R. Jones" <chris-SqNQQPNds68nxqbYAscKCQ@public.gmane.org>
Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: Containers roadmap?
Date: Mon, 6 Apr 2009 17:36:24 -0500	[thread overview]
Message-ID: <20090406223624.GA31708@us.ibm.com> (raw)
In-Reply-To: <20090406214127.GA1662-SqNQQPNds68nxqbYAscKCQ@public.gmane.org>

Quoting Chris R. Jones (chris-SqNQQPNds68nxqbYAscKCQ@public.gmane.org):
> One more question for the experts:
> 
> Is there any roadmap out there for when we can see containers support in 
> kernels for the major distributions (RHEL or SLES in our case)?
> 
> When will the feature be enabled by default in the linux kernels?
> (containers options aren't enabled by default in 2.6.29.1, for instance).
> 
> We've done some prototyping to get our application working with containers and 
> really like the solution.  But so far we've had to build our own kernel and 
> and really need to use kernels that come with the distribution.  
> 
> Any rough estimates when that will be the case?

I'm not gonna speak for any distros, but I definately can say that
the Fedora 11 beta has all the kernel features enabled.  Network
namespaces, even devpts namespaces.

-serge

      parent reply	other threads:[~2009-04-06 22:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-06 21:41 Containers roadmap? Chris R. Jones
     [not found] ` <20090406214127.GA1662-SqNQQPNds68nxqbYAscKCQ@public.gmane.org>
2009-04-06 22:36   ` Serge E. Hallyn [this message]

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=20090406223624.GA31708@us.ibm.com \
    --to=serue-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
    --cc=chris-SqNQQPNds68nxqbYAscKCQ@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox