You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is unclear to me whether this is a pure incus or zabbly-build bug. Feel free to tell me so I can file the bug upstream. :)
When installing incus in an unprivileged container, dnsmasq fails to create a unix socket due to it being blocked by the apparmor profile. This bug causes incus network create and incus admin init --auto to fail. Additionally, the bug appears to be specific to Ubuntu hosts as I couldn't reproduce it on Debian hosts.
Relevant dmesg output
Below, the dnsmasq apparmor profile is loaded by incus and the launch of dnsmasq causes a
Quite possibly some kind of apparmor kernel bug, we keep seeing apparmor enforce its profiles differently inside of containers than it does on the system directly...
It is unclear to me whether this is a pure incus or zabbly-build bug. Feel free to tell me so I can file the bug upstream. :)
When installing incus in an unprivileged container,
dnsmasq
fails to create a unix socket due to it being blocked by the apparmor profile. This bug causesincus network create
andincus admin init --auto
to fail. Additionally, the bug appears to be specific to Ubuntu hosts as I couldn't reproduce it on Debian hosts.Relevant dmesg output
Below, the dnsmasq apparmor profile is loaded by incus and the launch of
dnsmasq
causes aReplicating the bug
Note that using a bookworm VM instead of a jammy VM works.
The text was updated successfully, but these errors were encountered: