Users running 2.2 *already* have the apparmor=0 work around for *ephemeral* environments only.
For users running previous versions, we recommend you upgrade immediately, provided that 2.0 and 2.1 are out of support. If you decide not to upgrade, your options are:
@Frode,
Users running 2.2 *already* have the apparmor=0 work around for *ephemeral* environments only.
For users running previous versions, we recommend you upgrade immediately, provided that 2.0 and 2.1 are out of support. If you decide not to upgrade, your options are:
1. Use a HWE kernel (such as hwe-16.04). https:/ /bugs.launchpad .net/cloud- init/+bug/ 1701297/ comments/ 21
2. Use apparmor=0 as a global/machine kernel param (this will result in the deployed machine with apparmor disabled)
Marking this invalid for MAAS provided the bug is overlayfs.