title: Meet with CrashLoopBackOff and ContainerCreating status when apply contiv-vpp cni to k8s master node
body: <p>I'm using kubertenes version v1.21.2 to simply deploy a master node and a worker node respectly on KVM virtual machine(ubuntu 20.04 LTS).But after I run <code>kubectl apply -f </code> to apply contiv-vpp cni, some pods get status of CrashLoopBackOff and ContainerCreating.
  The two node are <code>Ready</code></p>
  <pre><code>NAME     STATUS   ROLES                  AGE   VERSION
  master   Ready    control-plane,master   20h   v1.21.2
  node     Ready    &lt;none&gt;                 17h   v1.21.2
  </code></pre>
  <p>I have run <code>kubectl get pods --all-namespaces</code> and the info as following:</p>
  <pre><code>NAMESPACE     NAME                             READY   STATUS              RESTARTS   AGE
  kube-system   contiv-crd-rlmjd                 1/1     Running             2          18h
  kube-system   contiv-etcd-0                    1/1     Running             2          18h
  kube-system   contiv-ksr-598zr                 1/1     Running             2          18h
  kube-system   contiv-vswitch-5pfjp             1/1     Running             0          17h
  kube-system   contiv-vswitch-hnbzx             0/1     CrashLoopBackOff    217        18h
  kube-system   coredns-558bd4d5db-46bvr         0/1     ContainerCreating   0          20h
  kube-system   coredns-558bd4d5db-t957f         0/1     ContainerCreating   0          20h
  kube-system   etcd-master                      1/1     Running             3          20h
  kube-system   kube-apiserver-master            1/1     Running             3          20h
  kube-system   kube-controller-manager-master   1/1     Running             3          20h
  kube-system   kube-proxy-5v4vj                 1/1     Running             0          17h
  kube-system   kube-proxy-7jkt6                 1/1     Running             3          20h
  kube-system   kube-scheduler-master            1/1     Running             3          20h
  </code></pre>
  <p>By <code>kubectl describe pod coredns-558bd4d5db-46bvr -n kube-system</code>, I find that the coredns pod keep <code>ContainerCreating</code> state due to message below:</p>
  <pre><code> Type     Reason                  Age                     From     Message
    ----     ------                  ----                    ----     -------
    Normal   SandboxChanged          8m31s (x957 over 88m)   kubelet  Pod sandbox changed, it will be killed and re-created.
    Warning  FailedCreatePodSandBox  3m29s (x1005 over 87m)  kubelet  (combined from similar events): Failed to create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container &quot;2a715c3aa43740540c1eae78d56f2eae6c75fc3bfe8c8f796c00867e4346a409&quot; network for pod &quot;coredns-558bd4d5db-46bvr&quot;: networkPlugin cni failed to set up pod &quot;coredns-558bd4d5db-46bvr_kube-system&quot; network: rpc error: code = Unavailable desc = connection error: desc = &quot;transport: Error while dialing dial unix /var/run/contiv/cni.sock: connect: no such file or directory&quot;
  </code></pre>
  <p>so is the another coredns pod.</p>
  <p>I think is quite clear that the question is lacking <code>cni.sock</code> file, but I donot know how to create or get it back.
  In the <code>contiv-vpp.yaml</code>(which have been applied by <code>kubectl apply -f</code>) I find a line that maybe result in this</p>
  <p><a href="https://i.stack.imgur.com/1oYfS.png" rel="nofollow noreferrer">enter image description here</a></p>
  <p>Remove this line and re-apply got the same status and message, still lack <code>cni.sock</code>.
  Please help me bros, I have google it for days and just can't fix it by myself.</p>