Update nerdctl and containerd together

[nirs]

nerdctl 2.1.x does not support containerd 2.2.x, so we should update containerd with nerdctl, or update containerd after nerdctl is updated.

• https://github.com/containerd/nerdctl/releases/tag/v2.2.0 - This release of nerdctl is expected to be used with containerd v1.7, v2.0, v2.1, or v2.2.
• https://github.com/containerd/nerdctl/releases/tag/v2.1.6 - This release of nerdctl is expected to be used with containerd v1.7, v2.0, or v2.1.

Possible fixes

• run both updates in the same PR, always updating to latest stable version of nerdctl and containerd, merging .github/workflows/update-nerdctl-version.yml and .github/workflows/update-containerd-version.yml
• skip containerd update if nerdctl is not updated to latest stable version, keeping current workflows
• Use nerdctl-full - Includes dependencies such as containerd, runc, and CNI

Merging the workflows

May be complicated, we try to generate a commit message about the update, and we have many combinations:

• containerd updated from version a1 to a2, nerdctl updated from version b1 to b2
• containerd updated from version a1 to a2
  • should we update? how do we know that nerdct is compatible with this version?
• nerdctl updated from version b1 to b2
• no update

Skipping containerd update

Skip if nerdctl needs an update. The next update is likely to pass.

Using nerdctl-full

The tarballs are huge:

• https://github.com/containerd/nerdctl/releases/download/v2.2.0/nerdctl-full-2.2.0-linux-amd64.tar.gz 262 MB
• https://github.com/containerd/nerdctl/releases/download/v2.2.0/nerdctl-full-2.2.0-linux-arm64.tar.gz 239 MB

[nirs]

/kind bug

[afbjorklund]

You could remove nerdctl and only use ctr (through minikube image), once nerdctld has been replaced with dockerd.

[nirs]

You could remove nerdctl and only use ctr (through minikube image), once nerdctld has been replaced with dockerd.

But ctr is a debugging tool, maybe better that crictl, but can we depend on it in minikube?

AI describes ctr as:

The ctr command-line tool is a low-level, unsupported administrative and debugging client for interacting directly with the containerd runtime daemon. It is bundled with containerd but is not intended for general end-user production use.

• https://github.com/containerd/containerd/blob/main/docs/getting-started.md#interacting-with-containerd-via-cli
• ctr: image pull without progress bar containerd/containerd#9664 (comment)
• really hope ctr supports rlimits containerd/containerd#7495 (comment)

[afbjorklund]

It could be useful to keep nerdctl around as a daemonless alternative (and docker-like), similar to podman for cri-o.