[lxc-devel] possible lxc-attach problem

S.Çağlar Onur caglar at 10ur.org
Sat Mar 1 01:55:43 UTC 2014


On Fri, Feb 28, 2014 at 7:21 PM, Serge Hallyn <serge.hallyn at ubuntu.com> wrote:
> Quoting Stéphane Graber (stgraber at ubuntu.com):
>> On Fri, Feb 28, 2014 at 06:11:25PM -0600, Serge Hallyn wrote:
>> > Quoting S.Çağlar Onur (caglar at 10ur.org):
>> > > On Fri, Feb 28, 2014 at 12:20 PM, Serge Hallyn <serge.hallyn at ubuntu.com> wrote:
>> > > > Quoting Serge Hallyn (serge.hallyn at ubuntu.com):
>> > > >> It seems to me these are the right things to do, but they'll take
>> > > >> some experimentation with the many possible hosts:
>> > > >>
>> > > >> 1. If / is not shared, do nothing
>> > > >> 2. if / is shared, and is not the ramfs, then remount MS_SLAVE|MS_REC
>> > > >> 3. if / is ramfs, then do the chroot_into_slave
>> > > >
>> > > > The following patch seems to work for me on arch.  It should
>> > > > also work on ubuntu as it makes no changes in the !shared
>> > > > path.  In order to fill in the ramfs root detection, could
>> > > > someone (Stéphane?) send the output of /proc/self/mountinfo
>> > > > on an android system?
>> > >
>> > > Yep, it looks much better on Fedora 20 as well
>> > > (http://paste.ubuntu.com/7013380/)
>> >
>> > Does lxc-attach also work with this patch on f20?
>>
>> Given Caglar's example is under lxc-attach, I'd think so :)
>
> Oh, yeah :)

Yep that output coming from fedora 20 running a fedora 20 container.

> Stéphane, can you send the /proc/self/mountinfo output
> for an android device?
> _______________________________________________
> lxc-devel mailing list
> lxc-devel at lists.linuxcontainers.org
> http://lists.linuxcontainers.org/listinfo/lxc-devel



-- 
S.Çağlar Onur <caglar at 10ur.org>


More information about the lxc-devel mailing list