runv fails to work with CRI-O

[Harshal Patil]

I try to plug runv with CRI-O it fails with following errors,

E1218 10:34:57.113034  110073 kubelet_volumes.go:128] Orphaned pod "2763e028-e3b0-11e7-9bf7-70e284141e65" found, but volume paths are still present on disk : There were a total of 3 errors similar to this. Turn up verbosity to see them.
I1218 10:34:57.914089  110073 worker.go:163] Probe target container not found: kube-dns-6c857864fb-smtlb_kube-system(a09aa123-e3b0-11e7-94a0-70e284141e65) - sidecar
I1218 10:34:58.876468  110073 worker.go:163] Probe target container not found: kube-dns-6c857864fb-smtlb_kube-system(a09aa123-e3b0-11e7-94a0-70e284141e65) - dnsmasq
E1218 10:34:59.108392  110073 kubelet_volumes.go:128] Orphaned pod "2763e028-e3b0-11e7-9bf7-70e284141e65" found, but volume paths are still present on disk : There were a total of 3 errors similar to this. Turn up verbosity to see them.
I1218 10:34:59.459553  110073 worker.go:163] Probe target container not found: kube-dns-6c857864fb-smtlb_kube-system(a09aa123-e3b0-11e7-94a0-70e284141e65) - kubedns

It doesn't launch shared containers in the same VM.

As per @gnawux the support should come in coming weeks. So I am just creating this issue here so that we can track the progress.

[Harshal Patil]

Closing this as it's a duplicate of #655