Update to runc v 1.0.3

[Letme]

What type of PR is this?

/kind bug
/kind regression

What this PR does / why we need it:

Current version (1.0.2) of runc prevents Kubernetes from running on RaspberryPi4 with non-hugetlb compiled kernel (standard Raspbian Bullseye). There is a fix inside Runc 1.0.3 for libct/cg/fs2: fix GetStats for unsupported hugetlb (opencontainers/runc#3233), which needs to be delivered to all existing supported Kubernetes versions (I tested v1.21.4 1.21.7 1.22.4 and 1.23.0).

Which issue(s) this PR fixes:

Fixes #

opencontainers/runc#3232

Special notes for your reviewer:

My first contribution, so I am not sure it is this simple.

Does this PR introduce a user-facing change?

Fix libct/cg/fs2: fix GetStats for unsupported hugetlb error on Raspbian Bullseye

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

[linux-foundation-easycla]

The committers are authorized under a signed CLA.

• ✅ Crt Mori (24b5bf2b80cc78e93d0da78004f9a0f6ccc7595c)

[k8s-ci-robot]

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
• If you have done the above and are still having issues with the CLA being reported as unsigned, please log a ticket with the Linux Foundation Helpdesk: https://support.linuxfoundation.org/
• Should you encounter any issues with the Linux Foundation Helpdesk, send a message to the backup e-mail support address at: login-issues@jira.linuxfoundation.org

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. I understand the commands that are listed here.

[k8s-ci-robot]

Welcome @Letme!

It looks like this is your first PR to kubernetes/kubernetes 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/kubernetes has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @Letme. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[Letme]

/check-cla

[pacoxu]

/sig node
/ok-to-test

[pacoxu]

You should run hack/lint-dependencies.sh to check dependencies before update.

To pin dependency version, you should try something like below.

hack/pin-dependency.sh github.com/opencontainers/runc v1.0.3
hack/update-vendor.sh

[pacoxu]

I did a quick example like https://github.com/kubernetes/kubernetes/compare/master...pacoxu:runc-v1.0.3?expand=1 that you can follow.

[Letme]

Thanks for the commands - I indeed did it by hand initially. So now with your commands I have cb7ff96e08c and I also ran the lint-dependencies as suggested and that also passed.

[ehashman]

/priority important-longterm
/triage accepted
/assign @kolyshkin

[Letme]

/ping on this... I would love to get it into update, so that I can get more nodes running.

[dims]

@SergeyKanzhelev did you get a chance to peek?

[SergeyKanzhelev]

Reviewed the release notes, looks good for master. I'm not sure about the cherry-picks though.

/lgtm
/assign @mrunalp

[SergeyKanzhelev]

/kind regression

@Letme do you know what version the issue was introduced in?

[kolyshkin]

/lgtm

[Letme]

@SergeyKanzhelev no, but I tested on all currently supported versions (v1.21.4 1.21.7 1.22.4 and 1.23.0) and it was there in all. So I would expect this to get cherry-picked for those versions.

[liggitt]

/approve
for dep update

/hold for @mrunalp ack if desired

I'm also unsure about the picks, especially to <= 1.21, since that was still on pre-1.0 runc RCs

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kolyshkin, Letme, liggitt

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:

• OWNERS [liggitt]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[mrunalp]

/lgtm
/cancel hold

[mrunalp]

/hold cancel

[k8s-triage-robot]

The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass.

This bot retests PRs for certain kubernetes repos according to the following rules:

• The PR does have any do-not-merge/* labels
• The PR does not have the needs-ok-to-test label
• The PR is mergeable (does not have a needs-rebase label)
• The PR is approved (has cncf-cla: yes, lgtm, approved labels)
• The PR is failing tests required for merge

You can:

• Review the full test history for this PR
• Prevent this bot from retesting with /lgtm cancel or /hold
• Help make our tests less flaky by following our Flaky Tests Guide

/retest

[pacoxu]

/skip

[Letme]

/retest

[k8s-ci-robot]

@Letme: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-kubernetes-integration	fadb36e	link	unknown	/test pull-kubernetes-integration

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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. I understand the commands that are listed here.

[Letme]

/test pull-kubernetes-integration

[Letme]

I am a bit puzzled why this was not added to recent 1.23.2 release. Can someone explain? It would fix and existing bug in all the currently supported versions on RaspberryPi's

[Letme]

/milestone v1.22
/milestone v1.23

[k8s-ci-robot]

@Letme: You must be a member of the kubernetes/milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your and have them propose you as an additional delegate for this responsibility.

In response to this:

/milestone v1.22
/milestone v1.23

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.