fix: guestagent audit detection and fallback #1855
Merged
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.
WSL2 just put out a new pre-release version (version 2.0.1 at the time of writing). While testing Lima with the new version, I noticed that AUDIT is enabled in the kernel:
and
cap_audit_read
/cap_audit_write
are set:However, lima-guestagent was now failing to start, probably for the same reason auditd was also failing to start.
After some digging, I found this excellent blog post (Google Translate helped out a lot), which led me in the right direction.
I've updated the lima-guestagent logic to detect this new case where auditing is enabled, but not permitted, and added links to the relevant source for reference.