support for unorchestrated rootfull and rootless Podman using OCI hook #1874
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
itsCheithanya
force-pushed
the
hook-test
branch
2 times, most recently
from
43d9216 to
e2c17e1
Compare
itsCheithanya
force-pushed
the
hook-test
branch
2 times, most recently
from
a67b446 to
137e1be
Compare
Signed-off-by: Cheithanya <cheithanya2002@gmail.com>
itsCheithanya
force-pushed
the
hook-test
branch
from
137e1be to
6dda08a
Compare
itsCheithanya
changed the title
|
Hi @itsCheithanya! Do you need some assistance over this? I also researched about Podman and would be happy to contribute for this! |
Thanks @Manik2708 but its ready and only need to be reviewed |
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.
Purpose of PR?:
This PR aims to handle enforcement for unorchestrated rootfull Podman containers using OCI hook
Fixes #1814
Does this PR introduce a breaking change?
If the changes in this PR are manually verified, list down the scenarios covered::
Additional information for reviewer? :
Mention if this PR is part of any design or a continuation of previous PRs
Checklist:
<type>(<scope>): <subject>