[Bug] It doesn't work fro containerd when I set cluster.registry.dataRoot

[life-]

What is version of KubeKey has the issue?

v2.1.0

What is your os environment?

CentOS 7

KubeKey config file

apiVersion: kubekey.kubesphere.io/v1alpha2
kind: Cluster
metadata:
  name: sample
spec:
  hosts:
  - {name: node1, address: 172.16.0.2, internalAddress: 172.16.0.2, user: ubuntu, password: "Qcloud@123"}
  - {name: node2, address: 172.16.0.3, internalAddress: 172.16.0.3, user: ubuntu, password: "Qcloud@123"}
  roleGroups:
    etcd:
    - node1
    control-plane:
    - node1
    worker:
    - node1
    - node2
  controlPlaneEndpoint:
    ## Internal loadbalancer for apiservers
    # internalLoadbalancer: haproxy

    domain: lb.kubesphere.local
    address: ""
    port: 6443
  kubernetes:
    version: v1.23.9
    clusterName: cluster.local
    autoRenewCerts: true
    containerManager: containerd
  etcd:
    type: kubekey
  network:
    plugin: calico
    kubePodsCIDR: 10.233.64.0/18
    kubeServiceCIDR: 10.233.0.0/18
    ## multus support. https://github.com/k8snetworkplumbingwg/multus-cni
    multusCNI:
      enabled: false
  registry:
    privateRegistry: ""
    namespaceOverride: ""
    registryMirrors: []
    insecureRegistries: []
    dataRoot: "/data/containerd"
  addons: []

A clear and concise description of what happend.

I change kubernetes.containerManager to containerd, and I set registry.dataRoot to another directory ("/data/containerd" in the example), but it does not work for containerd.

Relevant log output

No response

Additional information

No response

[24sama]

I checked this PR: https://github.com/kubesphere/kubekey/pull/1375/files
The dataRoot field is only for docker. So it's just a temporary method that configures the container manager in the .spec.registry.xxx. Maybe we will refactor the container manager configuration.

[life-]

Should I add dataRoot setting function for containerd current. Maybe you could tell me the plan of refactor container manager configuration. @24sama

[24sama]

Currently, welcome to create PR and follow the existed logic to configure the containerd, just like the above PR to configure the docker.
The work of code refactor maybe will not come soon, it's just an idea in my mind. If you have any great ideas or suggestions, welcome to leave some comments.

[life-]

/assign