Show information about the OCI container runtime

[afbjorklund]

There seems to some interest into which OCI container runtime (e.g. runc, crun)
that is being used by the CRI container runtime (e.g. docker, containerd, cri-o)

Maybe we should add a feature to the "cruntime" abstraction, to retreive this info ?
Then it could be displayed along with the other information, such as the version.

Currently we dump a hard-coded list, in minikube version --components

Related to: #11747 #12027

There is a slight confusion in terminology, with "container runtime" (engine) vs "container runtime" (runtime):

https://developers.redhat.com/blog/2018/02/22/container-terminology-practical-introduction#h.6yt1ex5wfo55

Container Runtime

A container runtime a lower level component typically used in a Container Engine but can also be used by hand for testing. The Open Containers Initiative (OCI) Runtime Standard reference implementation is runc. This is the most widely used container runtime, but there are others OCI compliant runtimes, such as crun, railcar, and katacontainers. Docker, CRI-O, and many other Container Engines rely on runc.

But we could show the information about which is being used, at least in the log file (if not in the UI) ?

I'm not sure where this actually makes a difference, but since we already show "runc" (and soon "crun")...

---

docker info | grep "Default Runtime"

Default Runtime: runc

containerd config dump | grep "runtime "

runtime = "runc"

crio config | grep ^default_runtime

default_runtime = "runc"

[afbjorklund]

In other news, runc was finally released (1.0) after being a Release Candidate for all this time... (5 years, since 2016)

https://github.com/opencontainers/runc/releases/tag/v1.0.0

https://github.com/opencontainers/runc/releases/tag/v1.0.0-rc1

Docker 20.10.8 was just released yesterday, including runc 1.0.1 and containerd 1.4.9 (that would be, on 2021-08-03)

[k8s-triage-robot]

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

This bot triages issues and 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 issue is closed

You can:

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

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

/lifecycle stale

[k8s-triage-robot]

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

This bot triages issues and 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 issue is closed

You can:

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

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

/lifecycle rotten

[klaases]

/remove-lifecycle rotten