run error when use containerd runtime

kubectl-debug --agentless --port-forward sentry-web-5f94694b8b-khkmg -n sentry

```
Agent Pod info: [Name:debug-agent-pod-61c2232b-4108-11ec-94e3-005056a34aea, Namespace:default, Image:aylei/debug-agent:latest, HostPort:10027, ContainerPort:10027]
Waiting for pod debug-agent-pod-61c2232b-4108-11ec-94e3-005056a34aea to run...
pod sentry-web-5f94694b8b-khkmg PodIP 10.233.95.181, agentPodIP 10.74.137.37
wait for forward port to debug agent ready...
Forwarding from 127.0.0.1:10027 -> 10027
Forwarding from [::1]:10027 -> 10027
Handling connection for 10027
Start deleting agent pod sentry-web-5f94694b8b-khkmg
end port-forward...
error execute remote, unable to upgrade connection: Failed to construct RuntimeManager. Error- failed to dial "/run/containerd/containerd.sock"- context deadline exceeded
error: unable to upgrade connection: Failed to construct RuntimeManager. Error- failed to dial "/run/containerd/containerd.sock"- context deadline exceeded

```

Start by reproducing the kubectl-debug --agentless --port-forward command against a containerd-based Kubernetes node and inspect the reported failure to dial /run/containerd/containerd.sock. Done means establishing whether containerd runtime support can be restored and confirming that the command completes without the RuntimeManager connection error.

Written by the indexing model from the issue text.