don't forcefully exec() docker version#6040
Merged
Merged
don't forcefully exec() docker version#6040
docker version#6040Conversation
dec7b4d to
31055e9
Compare
Member
|
Testing is a bit difficult at the moment because #5974 broke a test. |
… the first place. Less syscalls and more apparmor-friendly behavior
31055e9 to
0882b70
Compare
Codecov ReportAttention: Patch coverage is
📢 Thoughts on this report? Let us know! |
Author
|
ping? |
47 tasks
mrsdizzie
approved these changes
Apr 29, 2025
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
4 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.
If we don't intend to connect through docker, don't even exec() it in the first place: Less syscalls and more apparmor-friendly behavior