Due to a ping on IRC I wanted to summarize the situation here as it seems this still affects people.
In nested LXD container we seem to have multiple issues:
- apparmor service failing to start (might need to work with LXD to sort out why and how to fix it)
- if it doesn't work at least fail to start more gracefully
- comment 2 has a workaround to make dbus not insist on apparmor, but that is not a real fix we could generally apply
- snapd snapd.seeded.service needs code to die/exit gracefully in this situation (as it won't work)
- See comment 7, might have changed since then, but worth a revisit
Due to a ping on IRC I wanted to summarize the situation here as it seems this still affects people.
In nested LXD container we seem to have multiple issues:
- apparmor service failing to start (might need to work with LXD to sort out why and how to fix it)
- if it doesn't work at least fail to start more gracefully
- comment 2 has a workaround to make dbus not insist on apparmor, but that is not a real fix we could generally apply
- snapd snapd.seeded. service needs code to die/exit gracefully in this situation (as it won't work)
- See comment 7, might have changed since then, but worth a revisit