Learning containers from the bottom up
This is a great article.<p>I disagree with this:<p>> Now, when you have a decent understanding of containers - from both the implementation and usage standpoints - it's time to tell you the truth. Containers aren't Linux processes!<p>This is a bit of wordplay, I'm assuming, in absence of a word that defines the operating system features that power the <i>concept of containers</i>. To Linux, there is no (to my knowledge) concept of a "container". The container runtime runs your process(es) as the parent and uses the operating systems features to isolate it and restrict it/them. A virtual machine would just be a full emulated version of this, rather than using the operating system to virtualize the network stack. The author is right in that there is no such thing as a <i>container</i>, but only as much as <i>containing is a thing you do</i>, imo. What users think of containers are still just processes though, and I don't think that's an entirely useless abstraction to be cognizant of.