3 ms·

Container virtualization in Linux is actually quite old. First appearance in Linux around 2001: http://rhelblog.redhat.com/2015/08/28/the-history-of-containers/

Container virtualization in Linux is actually quite old. First appearance in Linux around 2001: http://rhelblog.redhat.com/2015/08/28/the-history-of-containers/ http://rhelblog.redhat.com/2015/08/28/the-history-of-contain... and the concept and real practice realization (in commercial products) of containers is even older. It has roots back to 1979! https://dzone.com/articles/evolution-of-linux-containers-future https://dzone.com/articles/evolution-of-linux-containers-fut... Docker is only a philosophy (one application in one container) and toolset around this containers. And docker itself is quite new in comparison. "This isn't a reason why DBs are a bad fit in itself, but it's a reason why running production data in Docker is a bad idea at present." You cannot say this in general. As everything in the world this really depends on what you are trying to achieve with your system.

cookiecaper 10y ago
Yeah, I understand that the concept of process isolation has existed for a long time. We used to know them as "chroot jails". cgroups obviously is a feature that has been dormant in the Linux kernel for a long time (until Docker came along and convinced everyone they had to use them, which actually isn't really a point in favor of containerization either: "we depend on this lightly tested feature of the kernel!"). Those things on their own are substantially different from what are today known as containers, a mix of concepts that involves custom daemons, complex network routing layers, bolt-on orchestration components like Swarm/Kube, and all sorts of other voodoo that makes today's understanding of "containers" distinct from historical uses either of the term or the concepts implemented via jails/zones/whatever.