fix: persistent apparmor linux-sandbox rule, write permission for pr check workflow#110
Merged
lurtz merged 2 commits intoeclipse-score:mainfrom Apr 13, 2026
Conversation
lurtz
changed the title
lurtz
changed the title
opajonk
approved these changes
Apr 13, 2026
|
🎉 This PR is included in version 1.4.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The linux-sandbox profile was not active after reboot. Most likely it is either because it was loaded before or after the profile, which disables Linux namespaces for most applications. With the aaa prefix it works when tested with
systemctl restart apparmor.service.The pr title workflow should write a comment, if the check fails. But the workflow lacked the write permission. With that it should work.