Actually lxc only appeared a few years before. It was based on original work in the kernel donated by IBM, who had originally intended it to be used to safely s

Actually lxc only appeared a few years before. It was based on original work in the kernel donated by IBM, who had originally intended it to be used to safely segregate the mega-resources on their mega-mainframes to individual non-mega workloads. (Source: I was using lxc a few years before, circa 2010, which is now 10 years ago. I had direct communications with the authors. I also submitted issues to docker outlining significant security issues early on, and made this summary of the space with skepticism around docker's already marketing-hype unreality: 'original post' and rest of page for context at http://stani.sh/walter/pfcts/ http://stani.sh/walter/pfcts/ ... the amusing thing is, the core solution identified (virtualization/topology/OS/local-remote paradigm neutral orchestration with CI/CD integration friendliness as a first class feature) is still painfully relevant and unfulfilled today, even as https://microk8s.io/ https://microk8s.io/ and similar make local work and some deployment easier, and the money in cloud IaaS services reaches 'staggering')