If you struggle to understand how all new container standards fit together, then watch Understanding Container Standards talk by Scott McCarty, where he even demos swapping one container engine with another without any loss of functionality. In addition, we also have Container Runtime Interface ( CRI) and Container Network Interface( CNI).

Since 2015 we have Open Containers Initiative (OCI) and specifications for how to run containers and manage container images. And we should give credit to Docker as a company for actually starting or actively supporting many of initiatives around standardization of container technology. Industry tries its best to avoid situation we have with virtualization technologies, where, despite having fantastic tools like libvirt, we still don't have a single set of standards that every virtualization provider would follow. Why would you not use Docker? Why would you use Docker? Are there really no alternatives to it? Did we - the IT-community - came up with the perfect solution for containers from the first attempt, right back in 2013? The title of this series - 'Dockerless' - requires an explanation. We'll be thrilled to be your guides on any part of this journey. Check it outĭevOps consulting: DevOps is a cultural and technological journey. UPDATE: After writing this series, I also made a video in which I show how to use Podman and Systemd to build and run containers. I will either elaborate in the reply or extend the article. If you still don't understand something, then drop a comment below the article.

If you don't understand some parts of the article, then follow all the links I put in the text. There are plenty of fantastic articles and videos out there and I will link the ones I find most useful. Disclaimer: I do not attempt to re-write existing content on topics like containers and containerization standards.

Alternative daemon tools open source