On Fri, May 29, 2015 at 11:37:35AM +0300, Vladimir Davydov wrote:
> >
> > No it can and it does run inside container (I notice some problems
> > though, regardless of how we represent cgroup paths inside container).
> > The main reason is to make /proc/pid/cgroup output to match what is
> > contai
On Fri, May 29, 2015 at 11:18:52AM +0300, Vladimir Davydov wrote:
> Hi Cyrill,
>
> On Tue, May 26, 2015 at 06:00:52PM +0300, Cyrill Gorcunov wrote:
> > We're bindmounting cgroups for container so if say a container
> > is having CTID=200 then @cgroups and @mountinfo output will
> > contain /200 as
On Tue, May 26, 2015 at 06:00:52PM +0300, Cyrill Gorcunov wrote:
> We're bindmounting cgroups for container so if say a container
> is having CTID=200 then @cgroups and @mountinfo output will
> contain /200 as a root. Which makes Docker to lookup for
> appropriate directory inside /sys/fs/cgroup/
>
On Fri, May 29, 2015 at 11:30:00AM +0300, Cyrill Gorcunov wrote:
> On Fri, May 29, 2015 at 11:18:52AM +0300, Vladimir Davydov wrote:
> > Hi Cyrill,
> >
> > On Tue, May 26, 2015 at 06:00:52PM +0300, Cyrill Gorcunov wrote:
> > > We're bindmounting cgroups for container so if say a container
> > > is
Hi Cyrill,
On Tue, May 26, 2015 at 06:00:52PM +0300, Cyrill Gorcunov wrote:
> We're bindmounting cgroups for container so if say a container
> is having CTID=200 then @cgroups and @mountinfo output will
> contain /200 as a root. Which makes Docker to lookup for
> appropriate directory inside /sys/
We're bindmounting cgroups for container so if say a container
is having CTID=200 then @cgroups and @mountinfo output will
contain /200 as a root. Which makes Docker to lookup for
appropriate directory inside /sys/fs/cgroup/
which of course not present because of been bindmounted
from the node (not
