hey, guys. I encounter a problem，here are the installation step and troubleshooting output. coz I am located on china, so using the INSTALL_K3S_MIRROR=cn when install. any idea?

$curl –sfL \
     <https://rancher-mirror.oss-cn-beijing.aliyuncs.com/k3s/k3s-install.sh> | \
     INSTALL_K3S_MIRROR=cn sh -s - \
     --system-default-registry="<http://registry.cn-hangzhou.aliyuncs.com|registry.cn-hangzhou.aliyuncs.com>" \
     --write-kubeconfig-mode="644"

$ kubectl get pods -A
NAMESPACE     NAME                                     READY   STATUS             RESTARTS         AGE
kube-system   helm-install-traefik-crd-d4wh2           0/1     CrashLoopBackOff   91 (2m46s ago)   7h17m
kube-system   local-path-provisioner-6f65f9b6d-ghwjq   0/1     CrashLoopBackOff   90 (2m5s ago)    7h17m
kube-system   metrics-server-7dbd8c95c-9tlxn           0/1     CrashLoopBackOff   91 (111s ago)    7h17m
kube-system   coredns-5cf45fb78d-b5hg4                 0/1     CrashLoopBackOff   91 (2m12s ago)   7h17m
kube-system   helm-install-traefik-5zqt9               0/1     CrashLoopBackOff   90 (2m31s ago)   7h17m

$ kubectl describe pod/coredns-5cf45fb78d-b5hg4 -n kube-system | less
Name:                 coredns-5cf45fb78d-b5hg4
Namespace:            kube-system
Priority:             2000000000
Priority Class Name:  system-cluster-critical
Service Account:      coredns
Node:                 c233dda3/192.168.9.124
Start Time:           Sat, 12 Aug 2023 00:56:21 +0800
Labels:               k8s-app=kube-dns
                      pod-template-hash=5cf45fb78d
Annotations:          <none>
Status:               Running
IP:                   10.42.0.93
IPs:
  IP:           10.42.0.93
Controlled By:  ReplicaSet/coredns-5cf45fb78d
Containers:
  coredns:
    Container ID:  <containerd://59fd07038db8c818b2d81ef2aa144fe9a8987ea0fb4ce12efe0679390eca0ef>2
    Image:         <http://registry.cn-hangzhou.aliyuncs.com/rancher/mirrored-coredns-coredns:1.10.1|registry.cn-hangzhou.aliyuncs.com/rancher/mirrored-coredns-coredns:1.10.1>
    Image ID:      <http://registry.cn-hangzhou.aliyuncs.com/rancher/mirrored-coredns-coredns@sha256:be7652ce0b43b1339f3d14d9b14af9f588578011092c1f7893bd55432d83a378|registry.cn-hangzhou.aliyuncs.com/rancher/mirrored-coredns-coredns@sha256:be7652ce0b43b1339f3d14d9b14af9f588578011092c1f7893bd55432d83a378>
    Ports:         53/UDP, 53/TCP, 9153/TCP
    Host Ports:    0/UDP, 0/TCP, 0/TCP
    Args:
      -conf
      /etc/coredns/Corefile
    State:          Waiting
      Reason:       CrashLoopBackOff
    Last State:     Terminated
      Reason:       StartError
      Message:      failed to create containerd task: failed to create shim task: OCI runtime create failed: runc create failed: unable to create new parent process: namespace path: lstat /proc/2303498/ns/ipc: no such file or directory: unknown
      Exit Code:    128
      Started:      Thu, 01 Jan 1970 08:00:00 +0800
      Finished:     Sat, 12 Aug 2023 08:06:28 +0800
    Ready:          False
    Restart Count:  90
    Limits:
...
Topology Spread Constraints:  <http://kubernetes.io/hostname:DoNotSchedule|kubernetes.io/hostname:DoNotSchedule> when max skew 1 is exceeded for selector k8s-app=kube-dns
Events:
  Type     Reason          Age                       From     Message
  ----     ------          ----                      ----     -------
  Warning  BackOff         28m (x7333 over 7h12m)    kubelet  Back-off restarting failed container coredns in pod coredns-5cf45fb78d-b5hg4_kube-system(cf661e77-83c7-4104-9740-a8841d18cfb9)
  Normal   Pulled          8m13s (x90 over 7h12m)    kubelet  Container image "<http://registry.cn-hangzhou.aliyuncs.com/rancher/mirrored-coredns-coredns:1.10.1|registry.cn-hangzhou.aliyuncs.com/rancher/mirrored-coredns-coredns:1.10.1>" already present on machine
  Normal   SandboxChanged  3m13s (x6410 over 7h12m)  kubelet  Pod sandbox changed, it will be killed and re-created.