There have been some strides made in implementing CRI-O compliant runtime engines. CoreOS (now owned by Red Hat) created rkt as a container runtime that improves on the security and standardization over docker.
Since EDCOP generally standardizes on CentOS/RHEL, it may make sense to implement rkt as the container runtime engine for EDCOP. A design proposal would be necessary to outline the advantages/disadvantages of implementing rkt over docker, and how to do it.
Some differences are outline in this CoreOS Blog Post, although these are likely biased toward rkt.
There have been some strides made in implementing CRI-O compliant runtime engines. CoreOS (now owned by Red Hat) created
rktas a container runtime that improves on the security and standardization over docker.Since EDCOP generally standardizes on CentOS/RHEL, it may make sense to implement rkt as the container runtime engine for EDCOP. A design proposal would be necessary to outline the advantages/disadvantages of implementing
rktoverdocker, and how to do it.Some differences are outline in this CoreOS Blog Post, although these are likely biased toward rkt.