Closed bboozzoo closed 2 years ago
Verified manually with the following layers:
meta
meta-poky
meta-yocto-bsp = "kirkstone:eaf8ce9d39a2c0d9c42b32fb6596ab4302f93a1a"
meta-oe
meta-filesystems
meta-perl
meta-python
meta-networking = "kirkstone:05dcac98473402d87e0af73bbc2c5a6a840abe93"
meta-security = "heads/bboozzoo/kirkstone:eea94d1ccc16f5542e46c1c5b61816385ca24ec8"
meta-snapd = "kirkstone:f7538c410cb657f00e94cc244c30ff00f9badda1"
The snapd.apparmor.service was not being added to the SYSTEMD_SERVICE list, even when apparmor was enabled in PACKAGECONFIG. This caused the service to not be auto-enabled and thus the apparmor profiles would not be loaded at the boot time.
Signed-off-by: Maciej Borzecki maciek@thing.com