Quoting Wolfgang Bumiller (w.bumil...@proxmox.com):
>
>
> > On September 7, 2015 at 5:44 PM Serge Hallyn
> > wrote:
> > Quoting Wolfgang Bumiller (w.bumil...@proxmox.com):
> > > On Fri, Sep 04, 2015 at 06:09:36PM +, Serge Hallyn wrote:
> > > > > I'm assuming the cleanup is left to the kerne
> On September 7, 2015 at 5:44 PM Serge Hallyn wrote:
> Quoting Wolfgang Bumiller (w.bumil...@proxmox.com):
> > On Fri, Sep 04, 2015 at 06:09:36PM +, Serge Hallyn wrote:
> > > > I'm assuming the cleanup is left to the kernel for when the last
> > > > reference to the namespace disappears. Ho
Quoting Wolfgang Bumiller (w.bumil...@proxmox.com):
> On Fri, Sep 04, 2015 at 06:09:36PM +, Serge Hallyn wrote:
> > > I'm assuming the cleanup is left to the kernel for when the last
> > > reference to the namespace disappears. However, this can be
> >
> > Yes.
> >
> > > problematic in some c
On Fri, Sep 04, 2015 at 06:09:36PM +, Serge Hallyn wrote:
> > I'm assuming the cleanup is left to the kernel for when the last
> > reference to the namespace disappears. However, this can be
>
> Yes.
>
> > problematic in some cases. For instance with an NFS mount, which can
> > apparently han
Quoting Wolfgang Bumiller (w.bumil...@proxmox.com):
> I can't seem to find much about the cleanup process of the mount
> namespace. And in fact, when I start a container, open
> /proc/$container/ns/mnt with another shell on the host, then stop the
> container (up to the point where lxc-info shows S
I can't seem to find much about the cleanup process of the mount
namespace. And in fact, when I start a container, open
/proc/$container/ns/mnt with another shell on the host, then stop the
container (up to the point where lxc-info shows STOPPED), then enter
the namespace via setns(2) I can still s
