-
-
Notifications
You must be signed in to change notification settings - Fork 254
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
Error when trying to modify a proxy device after last update: "Couldn't identify AppArmor cache directory" #1205
Comments
…sabled Closes lxc#1205 Signed-off-by: Stéphane Graber <[email protected]>
…sabled Closes lxc#1205 Signed-off-by: Stéphane Graber <[email protected]>
I assume this will be fixed in 6.6? Is there an older version to go back to that will work till than?
|
@jalbstmeijer the fix was merged but not released yet. Until a fix is released, the only way to bypass the error is to activate apparmor. If you are using raspbian, it is possible to activate by appending |
…sabled Closes #1205 Signed-off-by: Stéphane Graber <[email protected]>
@stgraber got a temporary fix? I am on void linux and they take forever to upstream shit with incus... |
Nope, the main options are:
|
…sabled Closes lxc#1205 Signed-off-by: Stéphane Graber <[email protected]>
Required information
Issue description
After the last update (IIRC I was on 0.7, now on 6.5, also updated a lot of other packages including kernel), I'm unable to make changes to the proxy devices due to "Couldn't identify AppArmor cache directory" . For example, I have a container called "dante-socks5-proxy ". This is what happens when I try to modify it
Steps to reproduce
Not sure how to reproduce, except that all containers I had in Incus 0.7 were affected by this after upgrading to 6.5. Apparently I can modify the configuration as long as I don't touch the proxy devices.
Information to attach
incus info NAME --show-log
)incus config show NAME --expanded
)Let me know if you need any more information that might be relevant to this error.
The text was updated successfully, but these errors were encountered: