Perhaps, but his title, and vast over simplification of the technologies he is trying to demystify is doing it all a huge disservice. Its like saying that a "Nuclear Reactor is just a steam turbine with marketing". Chroot was a very specific piece of technology that was nifty in its day, but the entire concept of how the kernel interfaces with processes had to be reworked to make namespaces work. Its not just "minor refinements and marketing" as he states. I appreciate that he is trying to show that "containers" just run in process space, but the approach is just overly simplified with no further explanation of just how simplified it is later on.

Ok, we've replaced the linkbaity title with a more representative sentence from the article.

If anyone can suggest a better title (i.e. more accurate and neutral, and using language from the article itself), we can change it again.

I wrote this and the consistent feedback I've gotten was that people hate the title, so thanks for changing it. I'd pick 'What chroot taught me about containers' but this also works.

Even better. Changed from "Let’s build a container runtime using only the chroot system call". Thanks!

Looks good to me

Thanks! ^_^