With the test kernel the observed failure is different. The snap in
question is installed in devmode so apparmor should be non-enforcing.
I tried to figure out exactly what is failing, I'll add a strace to
the mix to shed some more light.
Best regards
ZK
PS: Without the debug kernel the error is still the same as before.
On Thu, Jan 19, 2017 at 1:39 AM, Seth Arnold <email address hidden> wrote:
> Incidentally, the pastebins from comment #6 don't show the "Failed name
> lookup - disconnected path" -- based on what's visible there, I'm
> curious if this is just an incomplete profile?
>
> Thanks
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1656121
>
> Title:
> unexpected errno=13 and disconnected path when trying to open
> /proc/1/ns/mnt from a unshared mount namespace
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/apparmor/+bug/1656121/+subscriptions
Hey
With the test kernel the observed failure is different. The snap in
question is installed in devmode so apparmor should be non-enforcing.
I tried to figure out exactly what is failing, I'll add a strace to
the mix to shed some more light.
Best regards
ZK
PS: Without the debug kernel the error is still the same as before.
On Thu, Jan 19, 2017 at 1:39 AM, Seth Arnold <email address hidden> wrote: /bugs.launchpad .net/bugs/ 1656121 /bugs.launchpad .net/apparmor/ +bug/1656121/ +subscriptions
> Incidentally, the pastebins from comment #6 don't show the "Failed name
> lookup - disconnected path" -- based on what's visible there, I'm
> curious if this is just an incomplete profile?
>
> Thanks
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> unexpected errno=13 and disconnected path when trying to open
> /proc/1/ns/mnt from a unshared mount namespace
>
> To manage notifications about this bug go to:
> https:/