velad install --bind-ip=101.37.174.91 failed

[wonderflow]

root@iZbp1e3dhh5f4d0h13fesxZ:~# velad install --bind-ip=101.37.174.91
Preparing cluster setup script...
Preparing k3s binary...
Successfully place k3s binary to /usr/local/bin/k3s
Preparing k3s images
Successfully prepare k3s image
Setting up cluster...
[INFO]  Skipping k3s download and verify
[INFO]  Skipping installation of SELinux RPM
[INFO]  Skipping /usr/local/bin/kubectl symlink to k3s, already exists
[INFO]  Skipping /usr/local/bin/crictl symlink to k3s, already exists
[INFO]  Skipping /usr/local/bin/ctr symlink to k3s, command exists in PATH at /usr/bin/ctr
[INFO]  Creating killall script /usr/local/bin/k3s-killall.sh
[INFO]  Creating uninstall script /usr/local/bin/k3s-uninstall.sh
[INFO]  env: Creating environment file /etc/systemd/system/k3s.service.env
[INFO]  systemd: Creating service file /etc/systemd/system/k3s.service
[INFO]  systemd: Enabling k3s unit
Created symlink /etc/systemd/system/multi-user.target.wants/k3s.service → /etc/systemd/system/k3s.service.
[INFO]  systemd: Starting k3s
Successfully setup cluster
Generating kubeconfig for remote access into  /etc/rancher/k3s/k3s-external.yaml
Successfully generate kubeconfig at  /etc/rancher/k3s/k3s-external.yaml
Checking and installing vela CLI...
vela CLI is already installed, skip
ctr: failed to dial "/run/k3s/containerd/containerd.sock": connection error: desc = "transport: error while dialing: dial unix /run/k3s/containerd/containerd.sock: connect: connection refused"

Error: fail to load vela images: Fail to import image: exit status 1
Usage:
  velad install [flags]

Flags:
      --bind-ip string             Bind additional hostname or IP in the kubeconfig TLS cert
      --cluster-only               If set, start cluster without installing vela-core, typically used when restart a control plane where vela-core has been installed
      --controllers string         A list of controllers to enable, check "--controllers" argument for more spec in https://kubernetes.io/docs/reference/command-line-tools-reference/kube-controller-manager/ (default "*")
      --database-endpoint string   Use an external database to store control plane metadata, please ref https://rancher.com/docs/k3s/latest/en/installation/datastore/#datastore-endpoint-format-and-functionality for the format
  -d, --detail                     show detail log of installation (default true)
  -h, --help                       help for install
      --name string                The name of the cluster. only works when NOT in linux environment (default "default")
  -n, --namespace string           namespace scope for installing KubeVela Core (default "vela-system")
  -r, --reuse                      will re-use the user's last supplied values. (default true)
      --set stringArray            set values on the command line (can specify multiple or separate values with commas: key1=val1,key2=val2)
      --token string               Token for identify the cluster. Can be used to restart the control plane or register other node. If not set, random token will be generated

fail to load vela images: Fail to import image: exit status 1