4 ms·
Docker famously doesn't isolate very well, as known in infosec circles for years now. If you're unaware, search 'containers don't contain'. MicroVMs start fas
by nailer 7y ago
Docker famously doesn't isolate very well, as known in infosec circles for years now. If you're unaware, search 'containers don't contain'.
MicroVMs start faster and provide better isolation.
Meanwhile, none of this is relevant unless you're building your own cloud platform, which is a huge waste of time for most companies.
MicroVMs, containers, VMs, zones and bare metal are places to execute code. Serverless makes all those distinctions irrelevant.
Sorry if you spent 2015 getting really into Docker. You bet on the wrong horse. It's OK, this happens in tech.
Edit: if it's unclear, I don't mean Docker itself is the wrong horse, I mean containerisation tools per se are the wrong horse - and a bad place to invest your time unless you work for a cloud provider
- supermatt 7y agoAnd given recent revelations, VMs don't contain either! Docker is far from betting on the wrong horse. I can build a docker container and deploy/orchestrate it however I wish - via a docker runtime, kubernetes (which can vary in its underlying implementation), microVMs, VMs, or bare metal. But then the containers don't need to be docker either. Theres many options available there too. Either way, there are many options available. And the horse(s) are still in the running. As for "serverless" vs containers/other, if you can provision accordingly, containers/other can be a better option at scale. Horses for courses, I guess.
- nailer 7y agoSure, having a lot of VM knowledge is also irrelevant unless you're building your own cloud platform too. * Again, most people don't need to build their own cloud platform. Being able to reuse Docker files is nice, you've reinvented CFengine for the eighth time. That's great. The point is Docker is yet another standard way to build boxes and contain them. Serverless / FaaS platforms obviate that need. * obviously an isolated kernel is better than a shared one, but the point of this post (and this comment) is that Docker vs VM vs MicroVMs vs zones etc is irrelevant for companies who are not cloud providers
- hardwaresofton 7y agoYour point is actually the point I'm trying to make -- you shouldn't be using docker to try and contain possibly malicious code, it's not for that. It does isolate a process's view of the filesystem, it does isolate a process's view of the PID namespace, and that is valuable. Let's say it's a spectrum: raw processes -------- processes with a certain user ---------- namespace+cgroup isolated processes ---------------- VMs Docker is certainly an improvement for processes that you don't want running completely contained but want somewhat isolated. For isolation in every sense, you want a VM (a lightweight one if you can get it, i.e. some stripped down qemu). > MicroVMs start faster and provide better isolation. Agreed on isolation -- VMs are hands down better at isolating, but I'm a bit skeptical about starting faster. > Meanwhile, none of this is relevant unless you're building your own cloud platform, which is a huge waste of time for most companies. Again, this is exactly why it's relevant, 99% of people aren't building their own cloud platform, so they don't need the full isolation of VMs -- most of the time they're just trying to prevent program A that their devs wrote from clobbering program B that their devs also wrote when they both run on the same machine, and making it easier to deploy the dependencies that come with each. > MicroVMs, containers, VMs, zones and bare metal are places to execute code. Serverless makes all those distinctions irrelevant. OK I don't even really know what this means, you know serverless runs on MicroVMs right? and most of the time it's actually containers in MicroVMs? MicroVMs are just stripped down versions of regular VMs, and no one is in a zone unless they're running Solaris. The distinction between these things is still very important, unless you mean that the future is everyone just deploying functions for their applications? But even if you mean that, cold start is basically the first stumbling block you see and it literally exists because of the distinction between how these technologies work (and how fast they can be started on demand, with how much isolation). > Sorry if you spent 2015 getting really into Docker. You bet on the wrong horse. It's OK, this happens in tech. Is there anyone that spent 2015 really getting into Docker and isn't better for it now? The technologies that have sprung out of this part of computing are very valuable to know and are getting more valuable, not less. You don't have to install a VM to run an isolated postgres instance on your dev machine because containerization exists -- if you're still doing this you should probably look into updating your tooling. Also, don't forget that containerization is how some of the richest and supposedly best (due to their ability to spend money on engineers) companies in the world have been handling deployment for nearly a decade -- 2015 is late for realizing containerization is a good thing, not early.