k3s: update containerd version

[heywoodlh]

Resolves #391969 for me -- at the very least k3s is not crashing on startup with this PR.

I've only tried running k3s 1.32, should probably be tested with the other versions I updated but I'm unsure how best to do that most efficiently.

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

CC k3s maintainers:
@euank
@frederictobiasc
@marcusramberg
@Mic92
@rorosen
@wrmilling

---

Add a 👍 reaction to pull requests you find important.

[heywoodlh]

(Additionally, as a regular k3s user I'd be happy to add myself as a maintainer to k3s if more help is needed/desired)

[heywoodlh]

Spoke too soon, after a reboot my k3s cluster is still dead in the water. 😭 I'm going to put this in a draft phase for now.

[rorosen]

Thanks for the report.

Spoke too soon, after a reboot my k3s cluster is still dead in the water.

Yeah unfortunately this only overrides the containerd version used to build the containerd shim, so it won't overwrite the containerd version bundled into k3s. Have a look at #391969 (comment) for a quick workaround.

(Additionally, as a regular k3s user I'd be happy to add myself as a maintainer to k3s if more help is needed/desired)

That would be great! You only have to make a PR that adds yourself to the k3s maintainers. See the commit that added me as an example b9f397d