-
-
Notifications
You must be signed in to change notification settings - Fork 278
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
VM launch fails due to an AppArmor rule violation #1844
Comments
|
The instance profile that got generated:
|
Looks like I found the diff:
Not sure why it points to the |
The
|
|
I suspect one system has a pre-existing OVMF installation and the other one doesn't, but yeah, that suggests a regression on our end as the environment variable should take precedence on any locally available data. |
Reproduced the issue here |
Closes #1844 Signed-off-by: Stéphane Graber <[email protected]>
Verified with the latest build after recreating the VM:
Thanks a lot! |
Is there an existing issue for this?
Is this happening on an up to date version of Incus?
Incus system details
Instance details
Instance log
Current behavior
Checked the SHA256 on a working system and on a broken system - both are the same as below:
Expected behavior
A profile gets generated such that a VM can start.
Steps to reproduce
On the system where it happens it is enough to run
incus launch --vm images:ubuntu/24.04 <vm-name>
to reproduce.Trying to find a useful diff with a working system to understand why this started happening.
The text was updated successfully, but these errors were encountered: