[Bug 1401148] Re: Re/starting an lxc container corrupts all network namespaces on the same physical host

[Stefan Bader]

I had assumed that "test-test" was a type and saw the same result after
starting the container with "test", too. So somehow starting an lxc
container seems to have an impact on netns. Not sure whether the
apparmor message may relate which seems to trigger when lxc-start tries
to mount /run/netns.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1401148

Title:
  Re/starting an lxc container corrupts all network namespaces on the
  same physical host

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1401148/+subscriptions