-
-
Notifications
You must be signed in to change notification settings - Fork 13.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AppArmor fails to load with kernel 5.1.0 #61145
Comments
It can alternatively be reproduced with |
I can reproduce the apparmor issue (on unstable-small 19.09pre179342.0fe5e0279fe), but I can keep rebuilding once apparmor.service fails. Not sure if I'm understanding that part right though... |
Off the top of my head I'd guess that this is related to |
Hm, from my testing it seems that the selinux lsm is selected by the kernel at boot instead of apparmor for whatever reason under 5.1. I do note that Can you check Explicitly setting |
Otherwise we're subject to whatever defaults were selected at kernel build time. See also: NixOS#61145
I believe this has been fixed. Please reopen if the problem persists. |
Otherwise we're subject to whatever defaults were selected at kernel build time. See also: NixOS#61145
This is a problem again. Would somebody please re-open this issue? |
Hmmm, this seems to be fixed by a reboot. Is there some way to say "reboot required" from |
I just had the same issue and reboot indeed fixed it, thanks a lot |
Just reproduced this by adding Making a reboot unnecessary would be even better :-) Either way the problem still exists and significantly impacts usability... any plans on addressing it? |
Issue description
Upgrading to kernel 5.1.0 from
pkgs.linuxPackages_latest
breaks apparmor, preventing it from loading. Furthermore, this also breaksnixos-rebuild switch
, requiring a kernel downgrade topkgs.linuxPackages_5_0
(kernel 5.0.13) to fix this.The error is:
I believe the main issue is from this line here:
apparmor_parser[2996]: Cache read/write disabled: interface file missing. (Kernel needs AppArmor 2.4 compatibility patch.)
Steps to reproduce
boot.kernelPackages = pkgs.linuxPackages_latest;
andsecurity.apparmor.enable = true;
should be sufficient to reproduce the problem, although apparmor was already implicitly enabled on my system. I believe it's because of lxd.Technical details
The text was updated successfully, but these errors were encountered: