[BUG] When my k8s cluster (containerd runtime) host also has a docker runtime, kruise will recognize the k8s cluster runtime as docker

[J4sonZ]

What happened: When my k8s cluster (containerd runtime) host also has a docker runtime, kruise will recognize the k8s cluster runtime as docker

So in this case, I need to specify the sock path of containerd

What you expected to happen:

Kruise can automatically identify the real runtime of k8s without specifying parameters, instead of hard-coding the logic

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

• Kruise version:
• Kubernetes version (use kubectl version):
• Install details (e.g. helm install args):
• Others:

[J4sonZ]

Please add log