CRI-O vs containerd in Omnia

[sujit-jadhav]

We feel we should use CRI-O, it support building of images from Dockerfile using additional tools like 'Buildah' which is very easy to install and have no dependencies, and commands are almost similar to docker.

CRI-O	containerd
CRI-O is an implementation of the Kubernetes CRI (Container Runtime Interface) to enable using OCI (Open Container Initiative) compatible runtimes. CRI-O makes it possible for Kubernetes to run containers directly without much tools and code.	containerd is available as a daemon for Linux and Windows. It manages the complete container lifecycle of its host system.
CRI-O supports OCI container images and can pull from any container registry	containerd supports image push and pull functionality
CRI-O supports various tools such buildah for building images from dockerfile	Containerd does not build images from dockerfile
Networking for the pod is setup through use of CNI, so CNI plugin such as Flannel, Calico etc can be used with CRI-O.

[lwilson]

I am fine with using CRI-O. @j0hnL any concerns?

[lwilson]

Also, we have an issue open for this: #76. Let's be sure to comment in there once we make a determination and reference that issue when building the PR.