[#458] fix(sysdump): ensure AppArmor tar is gzipped in sysdump #460
+1
−1
Conversation
This file contains 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
Signed-off-by: Rishikesh <[email protected]>
rissh
force-pushed
the
sysdump-gzip-refactor
branch
from
afb5b76
to
844d84c
Compare
|
fixes #458 |
daemon1024
approved these changes
Sep 10, 2024
|
@rissh kindly handle the CI go-sec failure. |
Yup, I'm On it! |
|
Hey, sorry for the delay. I’ll get to it ASAP—just got caught up with something. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR fixes the issue where the
/etc/apparmor.ddirectory is being tarred but not gzipped in the KubeArmor sysdump process. The tarball generated was given a.tar.gzextension, but it was not actually gzipped.