Allow nerdctld on any driver

[afbjorklund]

It is already in the kicbase, and on the way for iso as well.

• Support docker-env with cri-o runtime #22547

• ISO: add nerdctld #22548

No need for artificial restrictions, it will fail if missing.

• make "docker-env" on containerd stable #22509

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: afbjorklund
Once this PR has been reviewed and has the lgtm label, please assign prezha for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[k8s-ci-robot]

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

Test name	Commit	Details	Required	Rerun command
integration-none-containerd-linux-x86	5b6a97e	link	false	/test integration-none-containerd-linux-x86
integration-docker-containerd-linux-x86	5b6a97e	link	true	/test integration-docker-containerd-linux-x86
integration-docker-containerd-linux-arm	5b6a97e	link	false	/test integration-docker-containerd-linux-arm
integration-none-docker-linux-x86	5b6a97e	link	true	/test integration-none-docker-linux-x86
integration-docker-docker-linux-arm	5b6a97e	link	true	/test integration-docker-docker-linux-arm
integration-docker-docker-linux-x86	5b6a97e	link	true	/test integration-docker-docker-linux-x86
integration-kvm-crio-linux-x86	5b6a97e	link	false	/test integration-kvm-crio-linux-x86
integration-kvm-docker-linux-x86	5b6a97e	link	true	/test integration-kvm-docker-linux-x86
integration-kvm-containerd-linux-x86	5b6a97e	link	true	/test integration-kvm-containerd-linux-x86
integration-docker-crio-linux-x86	5b6a97e	link	false	/test integration-docker-crio-linux-x86
pull-minikube-docker-containerd-linux-x86	5b6a97e	link	true	/test pull-minikube-docker-containerd-linux-x86
pull-minikube-docker-docker-linux-arm	5b6a97e	link	true	/test pull-minikube-docker-docker-linux-arm
pull-minikube-docker-docker-linux-x86	5b6a97e	link	true	/test pull-minikube-docker-docker-linux-x86
pull-minikube-kvm-docker-linux-x86	5b6a97e	link	true	/test pull-minikube-kvm-docker-linux-x86

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.

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

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale