"But I thought bocker implements Docker?" It doesn't, it only attempts to implement the "Docker daemon" part, and piggy-backs on Docker registries for image distribution. This is a huge part of the power of Docker, and why Docker isn't "just cgroups and namespaces". Cgroups and namespaces are a critical element, but Docker is much more than that too--it's also a set of standards for distributing and administering configuration+data for cgroups and namespaces.
Exactly. Containers were around for at least a decade before Docker, just like mp3's were around for decades before the iPod. Docker's simple, efficient way to package containers were the key to their explosion.
> , just like mp3's were around for decades before the iPod
That sounded wrong intuitively, so I decided to look it up: Wikipedia claims that mp3 was initially released in 1993, and the iPod was initially released in 2001, so not decades and not even a full decade.
Thanks for the correction. For some reason I thought that the patents on mp3 compression were issued in the 80's, but there's nothing in the Wikipedia article which specifically says that.
The point stands though, that Docker didn't invent containers by a long shot; but they did make them massively more useful.
I'd argue that bocker makes that more clear. It takes away any idea that the magic is in the containers. To the degree that it is, Linux provides that...not Docker.
It helps focus on what Docker does provide, as you mention.
Right that's a reasonable claim. bocker makes false claims though, which causes a bunch of confusion (which seems to be the case for the person I was replying to).
It makes it very clear what docker is, and isn't.
https://github.com/p8952/bocker
Specifically, the bocker_run function: https://github.com/p8952/bocker/blob/master/bocker#L61