-
Notifications
You must be signed in to change notification settings - Fork 41.5k
[1.27] Bump runc to 1.1.6 #117242
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
[1.27] Bump runc to 1.1.6 #117242
Conversation
Signed-off-by: Peter Hunt <[email protected]>
@haircommander could you please poke at why we are getting one more transitive dependency than we had before? Is there anything we can do about it? (submit a PR to update something or other in runc?) /assign @liggitt
|
I am honestly not sure. Is it possible it's coming from
this looks to be the same on master
If I were to guess it's similarly happened in #117095 though I'm struggling to find the job to prove that |
The same dep that @dims pointed out appears in #117241 so it's clearly coming from that 1.1.6 bump, see https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/117241/check-dependency-stats/1646141874617978880 |
@haircommander - if we bump
|
You can use Here's what the diagram looks like when run against runc repo: |
sorry, it's not clear to me what the ask is here. Are you suggesting we propose those changes to runc upstream and wait for a 1.1.7? |
So now that we know. Please open a PR to bump we don't need for them to tag that to land this. i am happy to go with this PR as-is as long as we update quickly when next |
I agree with this, though the master PR should be reviewed by sig-node and merge before merging this to release-1.27 |
💯 |
/sig node |
LGTM label has been added. Git tree hash: b5ce83c497733d72d20c8cd6bcaaef388514f70f
|
/approve |
/assign @kubernetes/release-managers |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: haircommander, liggitt, 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 |
xref: #117647 |
What type of PR is this?
/kind bug
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
cherry-picks of #117241 and #117095 for 1.27
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: