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.
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.