A good explainer on all the container specs floating about


OK, it's a little biased toward the CoreOS point of view. But this passage is well-stated and probably fair (if not a bit prejudiced):

Over the last three years, however, a plethora of integrations between Kubernetes and the Docker Engine have created dependencies that make assumptions about things like paths of logs to disks, Linux container internals, container image storage, and other subtle interactions.
Working out these dependencies will require adjustments and improved abstractions, which will take time to develop. And until these changes are made, any discussion of whether containerd, CRI-O, or any other CRI implementation is best for the Kubernetes community will remain theoretical for most production users.


Want to receive more content like this in your inbox?