From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tejun Heo Subject: Re: [PATCHv3 8/8] cgroup: Add documentation for cgroup namespaces Date: Wed, 11 Feb 2015 11:03:47 -0500 Message-ID: <20150211160347.GE21356@htj.duckdns.org> References: <20150107230615.GA28630@htj.dyndns.org> <87fvbm2nni.fsf@x220.int.ebiederm.org> <87y4peyxw5.fsf@x220.int.ebiederm.org> <20150107233553.GC28630@htj.dyndns.org> <20150211034616.GA25022@mail.hallyn.com> <20150211040957.GC21356@htj.duckdns.org> <20150211042942.GA27931@mail.hallyn.com> <87oap1qbv3.fsf@x220.int.ebiederm.org> <20150211051704.GB24897@mtj.duckdns.org> <20150211160023.GA1579@mail.hallyn.com> Mime-Version: 1.0 Return-path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=z9/fDqct4UKmhBv8U99RGqltxEXYDWT6pL++lRrrvGw=; b=Vs7OvGoiXqa153NhOUz2rWmMqRs1DUcmrq9pATY0MfVpDiMeeCoLO/OvFM4kuQekYa a3uyFgN+WEREcwNKVsGfTnntE5j6XlhGnQdavrC/qWiP5G7nKl/CuM6UQtZhu4EHZn9E 8Hw4cFvV3fScEb/Jn4GTybLkp98wmszJ7Fxq3yWBV76FfPm1pKiYZC+hL4dmmH6VFJXG FIhpX8WN8rsXUjS5E8g9+AR6oKsBtAR/RWgjMIouzYUafaeOZawycyD4s/eJ1i6x1dUN UC4EGcq9uwcqPN1U4I/pXFxNVb0LKjEmh2PCgWGLErRgRy2Exy80S5ItorWX/Nrn+IKo VZkQ== Content-Disposition: inline In-Reply-To: <20150211160023.GA1579-7LNsyQBKDXoIagZqoN9o3w@public.gmane.org> Sender: linux-api-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: "Serge E. Hallyn" Cc: "Eric W. Biederman" , Richard Weinberger , Linux API , Linux Containers , Serge Hallyn , "linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , Andy Lutomirski , cgroups mailinglist , Ingo Molnar On Wed, Feb 11, 2015 at 05:00:23PM +0100, Serge E. Hallyn wrote: > We absolutely would love to use cgroup namespaces to run older > userspace in containers. I don't know that it's actually possible > to do both that and use unified hierarchy at the same time though, > which is unfortunate. So an Ubuntu 12.04 container will never, afaics, > be able to run inside an ubuntu 16.04 host that is using unified > hierarchy, without using backported newer versions of lxc (etc) in > the container. So, the constraint there are the controllers. A controller can't be attached to two hierarchies at the same time for obvious reasons, so regardless of NS, you can't use the same controller on a unified hierarchy *and* a traditional hierarchy. NS doesn't adds or substracts from the situation. If you decide to attach a controller to a traditional hierarchy, that's where it's gonna be available. If you attach it to the unified hierarchy, the same story. Thanks. -- tejun