is containerd supported?

[hillbun]

What happened:

kubectl logs csi-plugin-pqv8x  -n kube-system -c oss-driver-registrar |more
I0325 03:58:34.518309 1347885 main.go:110] Version: v1.2.0-0-g6ef000ae
I0325 03:58:34.518417 1347885 main.go:120] Attempting to open a gRPC connection with: "/var/lib/kubelet/csi-plugins/ossplugin.csi.alibabacloud.com/csi.sock"
I0325 03:58:34.518459 1347885 connection.go:151] Connecting to unix:///var/lib/kubelet/csi-plugins/ossplugin.csi.alibabacloud.com/csi.sock
W0325 03:58:44.518963 1347885 connection.go:170] Still connecting to unix:///var/lib/kubelet/csi-plugins/ossplugin.csi.alibabacloud.com/csi.sock
W0325 03:58:54.518824 1347885 connection.go:170] Still connecting to unix:///var/lib/kubelet/csi-plugins/ossplugin.csi.alibabacloud.com/csi.sock
W0325 03:59:04.518740 1347885 connection.go:170] Still connecting to unix:///var/lib/kubelet/csi-plugins/ossplugin.csi.alibabacloud.com/csi.sock
W0325 03:59:14.518811 1347885 connection.go:170] Still connecting to unix:///var/lib/kubelet/csi-plugins/ossplugin.csi.alibabacloud.com/csi.sock
W0325 03:59:24.518737 1347885 connection.go:170] Still connecting to unix:///var/lib/kubelet/csi-plugins/ossplugin.csi.alibabacloud.com/csi.sock

deploy/oss/oss-plugin.yaml

    volumes:
       - name: registration-dir
         hostPath:
           #path: /var/lib/kubelet/plugins_registry
           path: /data/kubelet/plugins_registry
           type: DirectoryOrCreate
       - name: container-dir
         hostPath:
           #path: /var/lib/container
           path: /data/containerd/var/lib/containerd
           type: DirectoryOrCreate
       - name: kubelet-dir
         hostPath:
           path: /var/lib/kubelet
           type: Directory
       - name: host-dev
         hostPath:
           path: /dev
       - name: host-log
         hostPath:
           path: /var/log/
       - name: etc
         hostPath:
           path: /etc
       - name: ossconnectordir
         hostPath:
           path: /usr/

What you expected to happen:

csi-plugin pods should work properly

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

Anything else we need to know?:

Environment:

• Kubernetes version (use kubectl version):

v1.20.7

• Cloud provider or hardware configuration:
• OS (e.g: cat /etc/os-release):

NAME="Ubuntu" VERSION="21.04 (Hirsute Hippo)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 21.04" VERSION_ID="21.04"

• Kernel (e.g. uname -a):

Linux node1 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

• Install tools:
• Network plugin and version (if this is a network-related bug):
• Others:

[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

[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:

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

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

/close

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

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:

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

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

/close

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/test-infra repository.