3 ms·

We are there though. Currently there is no need to use docker to run containers natively in many OS. Systemd nspawn, rocket, cri-o accomplish the same workflo

We are there though. Currently there is no need to use docker to run containers natively in many OS. Systemd nspawn, rocket, cri-o accomplish the same workflows with tight OS integration. We don’t hear about them that much, but almost anyone using k8s is not using docker at this point.

orev 4y ago
You’ve completely missed the point. By “docker” they mean the concept of containers, which is only needed because developers are so absolutely awful at keeping track of what libraries they’re using, and completely opposed to using OS packages like rpm/deb, that someone (Docker) finally had to say “screw it, we’re just going to lump everything into this binary blob that includes a whole set of OS libraries because we just give up even trying to get them the play nice with the rest of the IT ecosystem”.
rileyphone 4y ago
Still the same problem, which is that the OS introduces a bunch of baggage that requires an additional layer of virtualization. To quote Dan Ingalls: > An operating system is a collection of things that don’t fit into a language. There shouldn’t be one.