runc 1.2.0 (and potentially earlier) is incompatible with golang 1.22

[haircommander]

What happened?

cross posting here for visibility opencontainers/runc#4233

What did you expect to happen?

the version of golang we use to build kube is compatible with newer versions

How can we reproduce it (as minimally and precisely as possible)?

attempt to build runc with 1.22, or kube with 1.21
xref cri-o/cri-o#7956

Anything else we need to know?

No response

Kubernetes version

$ kubectl version
# paste output here

v1.30

Cloud provider

all

OS version

only certain glibc versions

Install tools

Container runtime (CRI) and version (if applicable)

Related plugins (CNI, CSI, ...) and versions (if applicable)

[k8s-ci-robot]

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

[liggitt]

/remove-kind bug
/kind support

Latest kubernetes builds with latest go (unless there's a Kubernetes-impacting regression that requires us to stay on an earlier go version), if you need to build with go1.21 in the short-term, the Kubernetes 1.29 libraries are usable and still patched / maintained.

[liggitt]

/close

[k8s-ci-robot]

@liggitt: Closing this issue.

In response to this:

/close

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.

[haircommander]

note: this will affect users who use the same go to build kubernetes and runc. It's possible even older versions of runc are incompatible with the changes in go 1.22. There could be kubernetes regressions when it comes to calling runc

[liggitt]

kubernetes calls runc as a binary, not as a library, so the code in question is not part of the kubernetes build