I read it yesterday and I didn't like it; I think this post is a typical example of what happens with developers: the guy has a clear and pretty simple use case, a blog; he installs his blog in the wrong tool since the beginning and then he starts ranting over headless CMS and containers, but not because he needs a headless CMS on a container (he needs a blog), but just because its trendy to rant about headless CMS and containers and he wants to convince us he's a pretty smart ass that knows how to do everything the "right" way.
obviously there are use cases for a headless CMS (and containers), but I would like to bring back to your attention other articles I referenced in this post because, as one of the authors said there, "it’s not ‘headless or nothing’":
thanks for sharing!