** This bug is no longer a duplicate of bug 1660836
apparmor auditing denied access of special apparmor .null fi\ le
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654624
Title:
dhcp apparmor pr
*** This bug is a duplicate of bug 1660836 ***
https://bugs.launchpad.net/bugs/1660836
** This bug has been marked a duplicate of bug 1660836
apparmor auditing denied access of special apparmor .null fi\ le
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Hadmut, AppArmor's stacking support was intended to allow supporting
unmodified Ubuntu inside LXD containers. If you're feeling up for some
experimentation, you could try to disable this feature by setting the
kernel.unprivileged_userns_apparmor_policy sysctl to 0 early in a system
boot, preferably
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654624
Title:
dhcp apparmor profile complains about lxd client
To manage notifications about this bug go to:
https://
** Changed in: isc-dhcp (Ubuntu)
Importance: Undecided => High
** Changed in: apparmor (Ubuntu)
Importance: Undecided => High
** Changed in: apparmor (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
> Which are the perceivable consequences of this bug?
I currently cannot survey the consequences, since I am not familiar with
the recent semantic changes of apparmor (are there any docs? Any hints
to the users about changes? Any release notes?)
For some time now I am spending and wasting lots of
> Removing the LXD task, this is yet another apparmor bug from the apparmor
> stacking/namespacing change which was backported to Xenial.
Well, that explains a lot. 16.04 was formerly stable but recently began to
drive me crazy because of so many apparmor problems with almost every major
daemo
Removing the LXD task, this is yet another apparmor bug from the
apparmor stacking/namespacing change which was backported to Xenial.
Basically, dhclient is now being confined by apparmor inside the
container, unfortunately, apparmor doesn't behave in the exact same way
when it's interpreting a pr
** Also affects: lxd (Ubuntu)
Importance: Undecided
Status: New
** Also affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
Which are the perceivable consequences of this bug?
When answered please set status back to "confirmed". Thank you.
** Summary changed:
- dhcp apparmor profile comlains about lxd client
+ dhcp apparmor profile complains about lxd client
** Changed in: isc-dhcp (Ubuntu)
Status: Confirmed
10 matches
Mail list logo
