k3s crictl broken with crio

[de13]

Describe the bug

I've started a cluster with crio following the steps described here #107. Some pods successfully runs on the cluster, but `k3s crictl ps' returns an error:

$ k3s kubectl get po --all-namespaces
NAMESPACE     NAME                       READY   STATUS              RESTARTS   AGE
kube-system   coredns-7748f7f6df-8nzpj   0/1     ContainerCreating   0          30m
kube-system   weave-net-bswx2            2/2     Running             0          29m
$ cat /etc/crictl.yaml
runtime-endpoint: unix:///var/run/crio/crio.sock
$ k3s crictl ps
FATA[2019-03-11T21:08:02.180159249+01:00] failed to connect: failed to connect: context deadline exceeded

To Reproduce

sudo k3s server --disable-agent --no-deploy traefik --container-runtime-endpoint=/run/crio/crio.sock

Expected behavior

The output from the command.

[de13]

my bad, sudo k3s crictl ps works as expected