Skip to content

Conversation

@saschagrunert
Copy link
Contributor

The latest NRI wasm support will require go 1.24. Means we switch to the latest golang minor ahead of time to allow seamless upgrades.

Refers to containerd/nri#148

The latest NRI wasm support will require go 1.24. Means we switch to the
latest golang minor ahead of time to allow seamless upgrades.

Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
@k8s-ci-robot
Copy link

Hi @saschagrunert. Thanks for your PR.

I'm waiting for a containerd 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.

Details

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-sigs/prow repository.

@dosubot dosubot bot added the go Pull requests that update Go code label Mar 12, 2025
module github.com/containerd/containerd/v2

go 1.23.0
go 1.24
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I still have to look into the NRI side of changes. But this will force the minimal version to 1.24. Is it possible to keep the go.mod version at 1.23 in NRI and toolchain at 1.24?

@samuelkarp
Copy link
Member

Copying my comment over from containerd/nri#148 (comment)

this will also be a breaking change, WASM plugins compiled with tinygo will not work with golang ones because the underlying library changed
[...]
Proposing the new golang version in #11533

Oof. So for containerd, either we:

  1. Require 1.24 in 2.1 (which can make it hard for distros to ship 2.1, delaying adoption), or
  2. Don't take 1.24 in 2.1 and ship 2.1 with the initial tinygo-based WASM support, and then immediately break that in the next release (2.2)
  3. Disable WASM in 2.1 and take the 1.24 minimum version change in 2.2 (which will be more reasonable timing-wise as Go 1.23 will have reached EOL)

None of those sound like great choices to me. I think option 2 sounds the worst though.

@samuelkarp
Copy link
Member

Per the community call today, we do not plan to require Go 1.24 in containerd 2.1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

go Pull requests that update Go code needs-ok-to-test size/XS

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

4 participants