[Bug 1667016] Re: tcpdump in lxd container: apparmor blocks writing to stdout/stderr

2019-06-13 Thread Brian Candler
*** This bug is a duplicate of bug 1641236 *** https://bugs.launchpad.net/bugs/1641236 I believe this bug has been wrongly marked as a duplicate of #1641236. I described in the second paragraph of the bug report why this is *not* a duplicate. #1641236 is when lxc exec passes an open pty from

[Bug 1667016] Re: tcpdump in lxd container: apparmor blocks writing to stdout/stderr

2019-02-15 Thread Stéphane Graber
*** This bug is a duplicate of bug 1641236 *** https://bugs.launchpad.net/bugs/1641236 ** This bug has been marked a duplicate of bug 1641236 Confined processes inside container cannot fully access host pty device passed in by lxc exec -- You received this bug notification because you

[Bug 1667016] Re: tcpdump in lxd container: apparmor blocks writing to stdout/stderr

2017-09-15 Thread Jacek Nykis
** Tags added: canonical-bootstack -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667016 Title: tcpdump in lxd container: apparmor blocks writing to stdout/stderr To manage notifications about

[Bug 1667016] Re: tcpdump in lxd container: apparmor blocks writing to stdout/stderr

2017-02-22 Thread Seth Arnold
Top-notch bug report :) Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667016 Title: tcpdump in lxd container: apparmor blocks writing to stdout/stderr To manage notifications about this

[Bug 1667016] Re: tcpdump in lxd container: apparmor blocks writing to stdout/stderr

2017-02-22 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apparmor (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667016 Title: