-
Notifications
You must be signed in to change notification settings - Fork 501
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use package runtime dependencies for CRI-O #3282
Conversation
We now use `conmon` and `crun` as package dependencies to not clash with packages like `podman`. We also need a common (`golang-github-containers-common`/`containers-common`) as dependencie to avoid writing `policy.json` and `registries.conf`. Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
/override pull-release-integration-test This test needs an update. |
@saschagrunert: Overrode contexts on behalf of saschagrunert: pull-release-integration-test In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@kubernetes/release-engineering PTAL |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cpanato, saschagrunert The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind bug
What this PR does / why we need it:
We now use
conmon
andcrun
as package dependencies to not clash with packages likepodman
. We also need a common(
golang-github-containers-common
/containers-common
) as dependencie to avoid writingpolicy.json
andregistries.conf
.Which issue(s) this PR fixes:
None
Special notes for your reviewer:
None
Does this PR introduce a user-facing change?