Skip to content

Pull requests: cri-o/cri-o

New pull request New
41 Open 6,761 Closed
41 Open 6,761 Closed
Author
Filter by author
Label
Filter by label
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Milestones
Filter by milestone
Reviews
Filter by reviews
No reviews Review required Approved review Changes requested
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Pull requests list

Bump version to 1.30.2 dco-signoff: yes Indicates the PR's author has DCO signed all their commits. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. release-note-none Denotes a PR that doesn't merit a release note.
#8237 opened Jun 1, 2024 by github-actions bot Loading…
2
[release-1.25] OCPBUGS-33808: server: use SecureJoin when setting container /etc directory dco-signoff: yes Indicates the PR's author has DCO signed all their commits. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. release-note Denotes a PR that will be considered when it comes time to generate release notes.
#8236 opened May 31, 2024 by kwilczynski Loading…
@kwilczynski @haircommander
5
[release-1.26] OCPBUGS-33809: server: use SecureJoin when setting container /etc directory dco-signoff: yes Indicates the PR's author has DCO signed all their commits. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. release-note Denotes a PR that will be considered when it comes time to generate release notes.
#8235 opened May 31, 2024 by kwilczynski Loading…
@kwilczynski @haircommander
5
[release-1.25] Cherry-pick changes from containers/image/pull#2418 dco-signoff: yes Indicates the PR's author has DCO signed all their commits. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. kind/bug Categorizes issue or PR as related to a bug. release-note-none Denotes a PR that doesn't merit a release note.
#8224 opened May 28, 2024 by kwilczynski Loading…
@kwilczynski
3
[release-1.26] Cherry-pick changes from containers/image/pull#2418 dco-signoff: yes Indicates the PR's author has DCO signed all their commits. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. kind/bug Categorizes issue or PR as related to a bug. release-note-none Denotes a PR that doesn't merit a release note.
#8223 opened May 28, 2024 by kwilczynski Loading…
@kwilczynski
3
[WIP] [release-1.27] Cherry-pick changes from containers/image/pull#2418 dco-signoff: yes Indicates the PR's author has DCO signed all their commits. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. kind/bug Categorizes issue or PR as related to a bug. release-note-none Denotes a PR that doesn't merit a release note.
#8222 opened May 28, 2024 by kwilczynski Loading…
@kwilczynski
3
[WIP] [release-1.28] Cherry-pick changes from containers/image/pull#2418 dco-signoff: yes Indicates the PR's author has DCO signed all their commits. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. kind/bug Categorizes issue or PR as related to a bug. release-note-none Denotes a PR that doesn't merit a release note.
#8221 opened May 28, 2024 by kwilczynski Loading…
@kwilczynski
6
add mermaid flow diagram for patch releases approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. kind/documentation Categorizes issue or PR as related to documentation. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. release-note-none Denotes a PR that doesn't merit a release note.
#8220 opened May 28, 2024 by olad5 Loading…
@saschagrunert @olad5
29
[release-1.29] Cherry-pick changes from containers/image/pull#2418 approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. kind/bug Categorizes issue or PR as related to a bug. release-note-none Denotes a PR that doesn't merit a release note.
#8219 opened May 28, 2024 by kwilczynski Loading…
@kwilczynski
4
[release-1.30] Cherry-pick changes from containers/image/pull#2418 approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. kind/bug Categorizes issue or PR as related to a bug. release-note-none Denotes a PR that doesn't merit a release note.
#8218 opened May 28, 2024 by kwilczynski Loading…
@kwilczynski
6
updates pause image to 3.10 dco-signoff: yes Indicates the PR's author has DCO signed all their commits. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. kind/dependency-change Categorizes issue or PR as related to changing dependencies lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. release-note Denotes a PR that will be considered when it comes time to generate release notes.
#8215 opened May 25, 2024 by tukwila Loading…
@kwilczynski @tukwila
11
Reload config should remove pinned images when an empty list is provided dco-signoff: yes Indicates the PR's author has DCO signed all their commits. kind/bug Categorizes issue or PR as related to a bug. release-note Denotes a PR that will be considered when it comes time to generate release notes.
#8213 opened May 24, 2024 by roman-kiselenko Loading…
1
@kwilczynski @roman-kiselenko
12
WIP: image verificaiton for namespaced policies dco-signoff: yes Indicates the PR's author has DCO signed all their commits. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress.
#8212 opened May 23, 2024 by harche • Draft
4
build(deps): bump ocicni to v0.4.3 dco-signoff: yes Indicates the PR's author has DCO signed all their commits. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. kind/dependency-change Categorizes issue or PR as related to changing dependencies needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. release-note-none Denotes a PR that doesn't merit a release note.
#8207 opened May 22, 2024 by maiqueb • Draft
7
contrib/cni/*: Change CNI config to latest spec dco-signoff: yes Indicates the PR's author has DCO signed all their commits. kind/documentation Categorizes issue or PR as related to documentation. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. release-note-none Denotes a PR that doesn't merit a release note.
#8204 opened May 21, 2024 by PannagaRao Loading…
@PannagaRao
7
test: use config file rather than environment variables for the kata CI job dco-signoff: yes Indicates the PR's author has DCO signed all their commits. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. kind/ci Categorizes issue or PR as related to CI release-note-none Denotes a PR that doesn't merit a release note.
#8166 opened May 13, 2024 by littlejawa Loading…
24
Topic/docs completions config updates for runtime pull image approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. release-note Denotes a PR that will be considered when it comes time to generate release notes.
#8110 opened May 2, 2024 by fidencio Loading…
8
[WIP] Replace the built-in Go map with SwissMap in ResourceStore dco-signoff: yes Indicates the PR's author has DCO signed all their commits. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. kind/feature Categorizes issue or PR as related to a new feature. release-note-none Denotes a PR that doesn't merit a release note.
#8101 opened May 1, 2024 by kwilczynski Loading…
@kwilczynski
8
Filter namespace creation args to clone in default seccomp policy dco-signoff: yes Indicates the PR's author has DCO signed all their commits. kind/bug Categorizes issue or PR as related to a bug. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. release-note Denotes a PR that will be considered when it comes time to generate release notes.
#8054 opened Apr 22, 2024 by dgl Loading…
6
[DRAFT] Confidential Containers - Skip pullimage for runtimes that are handling it dco-signoff: yes Indicates the PR's author has DCO signed all their commits. kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. release-note-none Denotes a PR that doesn't merit a release note.
#8008 opened Apr 12, 2024 by littlejawa Loading…
3
test: use kata 3.3.0 for testing dco-signoff: yes Indicates the PR's author has DCO signed all their commits. kind/ci Categorizes issue or PR as related to CI lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. release-note-none Denotes a PR that doesn't merit a release note.
#7958 opened Apr 3, 2024 by littlejawa Loading…
@kwilczynski @littlejawa
18
Add cri-o-runc source to install.md dco-signoff: yes Indicates the PR's author has DCO signed all their commits. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test.
#7941 opened Mar 27, 2024 by tvorogme Loading…
9
Save CRIU restore.log dco-signoff: yes Indicates the PR's author has DCO signed all their commits. kind/other Categorizes issue or PR as not clearly related to any existing kind/* category release-note Denotes a PR that will be considered when it comes time to generate release notes.
#7904 opened Mar 18, 2024 by adrianreber Loading…
15
WIP: Add conmon-rs streaming server support approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. release-note Denotes a PR that will be considered when it comes time to generate release notes.
#7903 opened Mar 18, 2024 by saschagrunert Loading…
3
[WIP-Refactor part 1] Move container mounts to internal/factory/container dco-signoff: no Indicates the PR's author has not DCO signed all their commits. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API kind/ci Categorizes issue or PR as related to CI kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. kind/other Categorizes issue or PR as not clearly related to any existing kind/* category needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. release-note-none Denotes a PR that doesn't merit a release note.
#7859 opened Mar 11, 2024 by hasan4791 Loading…
1
16
ProTip! Type g p on any issue or pull request to go back to the pull request listing page.