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
apparmor.service being enabled by default in the images causes various issues (e.g. https://gitlab.com/apparmor/apparmor/-/issues/402). Given these are ephemeral build VMs where users have full root access already and can trivially disable apparmor anyway, there's no real point in having apparmor enabled. It only serves to cause hard to debug issues. To avoid others running into these issues, I propose to disable apparmor in the runner images.
Platforms affected
Azure DevOps
GitHub Actions - Standard Runners
GitHub Actions - Larger Runners
Runner images affected
Ubuntu 20.04
Ubuntu 22.04
Ubuntu 24.04
macOS 11
macOS 12
macOS 13
macOS 13 Arm64
macOS 14
macOS 14 Arm64
Windows Server 2019
Windows Server 2022
Image version and build link
latest
Is it regression?
no
Expected behavior
apparmor is disabled by default
Actual behavior
apparmor is enabled by default
Repro steps
Run job
systemctl status apparmor will show that it is running
The text was updated successfully, but these errors were encountered:
Description
apparmor.service being enabled by default in the images causes various issues (e.g. https://gitlab.com/apparmor/apparmor/-/issues/402). Given these are ephemeral build VMs where users have full root access already and can trivially disable apparmor anyway, there's no real point in having apparmor enabled. It only serves to cause hard to debug issues. To avoid others running into these issues, I propose to disable apparmor in the runner images.
Platforms affected
Runner images affected
Image version and build link
latest
Is it regression?
no
Expected behavior
apparmor is disabled by default
Actual behavior
apparmor is enabled by default
Repro steps
The text was updated successfully, but these errors were encountered: