5 ms·
Yup. It's all namespaces and cgroups. The base "docker" command adds a little value with os respositories, network overlays, etc, but not a lot. Personally, I
by tyingq 9y ago
Yup. It's all namespaces and cgroups. The base "docker" command adds a little value with os respositories, network overlays, etc, but not a lot.
Personally, I think K8S with their cri-o (https://github.com/kubernetes-incubator/cri-o/blob/master/README.md https://github.com/kubernetes-incubator/cri-o/blob/master/RE...) runtime is going to eventually eat Docker's lunch.
As a company, Docker needs Swarm/Enterprise to take off in order to have a differentiator. That isn't happening.
Kubernetes, on the other hand, just needs cri-o (mostly done) and an image repository / builder to kill off Docker.
See this for how small the gap really is: https://github.com/p8952/bocker/blob/master/README.md https://github.com/p8952/bocker/blob/master/README.md
Basically, Docker has almost no moat. They have mostly only brand recognition. Not discounting their efforts, but they are playing checkers and Google is playing chess.
- hardwaresofton 9y agoI think this is how I most commonly recognize someone that is familiar with lxc +/- docker and containerization in general. A firm grasp of the fact that they're just beefy processes, isolated wiht namespaces and cgroups is the best, most succint way to describe docker (without even mentioning the benefits), but it also requires that the hearer knows what namespaces and cgroups are. If I had to rank understanding in explanations of docker: 1. "Makes your application really portable"/other explanations that only cover the benefits of docker not how it works 2. "Lightweight VMs" 3. "LXC + some other stuff" 4. "processes + namespaces + cgroups (+/- image management tools, etc)" 100% agreed on the point you made, pretty sure docker+swarm and other orchestration efforts have basically lost the competition. Kubernetes just has the mind share, and even better than that -- it's actually good. Kubernetes also has multiple competing container runtimes all rushing to fit the CRI (Container Runtime Interface). Just some of the stuff out there: * cri-containerd - https://github.com/containerd/cri-containerd https://github.com/containerd/cri-containerd * runv (hypervisor based) - https://github.com/hyperhq/runv https://github.com/hyperhq/runv * clear containers (hypervisor based) - https://github.com/clearcontainers/runtime https://github.com/clearcontainers/runtime * kata containers (hypervisor based, collaboration of runv + clear container) - https://katacontainers.io/ https://katacontainers.io/ * frakti (combination of runv & docker, enabling switching @ runtime) - https://github.com/kubernetes/frakti https://github.com/kubernetes/frakti A bunch of the projects are in their infancy, but the CNCF/kubernetes and the community are doing the right thing investing in lots of them, and letting the good ones bubble to the top. I don't run a production kubernetes cluster but I've found cri-containerd to be really easy to use and haven't had any major problems with it, mostly small configuration things. The last one, frakti, gets me really excited, because it lets you be flexible about which containers run in more protected environments and which don't. Also really exciting is frakti v2 (https://github.com/kubernetes/frakti/tree/containerd-kata https://github.com/kubernetes/frakti/tree/containerd-kata), which is kata + containerd.
- tyingq 9y agoKinda feels like I'm I a foreign country and run into someone that speaks my language :). Thanks for the additional info, like frakti, for example...didn't know about that. Explaining docker is frustrating for me because I was a Unix admin back in the 90's. So, for me, it's pretty easy to see what it is. And, it isn't new. There isn't much it does that Solaris zones or BSD jails, didn't do. And those predate docker by years. Namespaces, cgroups, and pivot_root. That's basically all of it. Kudos to docker for marketing it better. Explaining it, on the other hand, to a broad audience...
- hardwaresofton 9y agoYeah I didn't either, until not too long ago but now I'm pretty excited to use it. As a person who wasn't a linux admin back in the 90s, and doesn't normally hang out on mailing lists, the first time I saw lxc was some random article on lwn.net (I don't hang out there, but they have some super high quality articles), and I definitely didn't put together how much of a difference it was poised to make, or even know why it was a good idea (people were still getting used to vagrant everywhere at the time) -- docker definitely did the community a service by bringing the hype train, if only so that once the hype subsided containers would be here to stay.
- Annatar 9y agoAs a person who wasn't a linux admin back in the 90s, Nobody was a Linux admin in the ‘90’s: we ran HP-UX, IRIX, OSF/1 DECUnix (and Ultrix), AIX, Solaris and NetBSD; those were our Linux we grew up on like you grew up on a Linux ISO on your parents’ PC bucket.
- js2 9y agoI ran a small ISP on a pair of Linux (Slackware probably) boxes, a Livingston Portmaster, a bank of Hayes modems, and a T1 in the mid-90s. So some of us were Linux admins then.
- deleted 9y ago[deleted]
- yoz-y 9y agoOne important thing for me is that Docker also handles other operating systems than Linux through their respective hypervisors. Docker might well die but first I will have to be able to locally build and test containers on Windows and macOS, before deploying them to the Kubernetes cluster–without fooling around with Virtualbox, Vagrant and the like.
- raesene9 9y agoWell they have multi-platform. Windows containers are intrinsically tied up with Docker (the current Windows containers docs start with a Docker EE Basic install). My personal expectation is that Docker will be bought by Microsoft, probably this year or next ...
- imtringued 9y ago>Basically, Docker has almost no moat. They have mostly only brand recognition. Not discounting their efforts, but they are playing checkers and Google is playing chess. Well how do you build images without docker?
- tyingq 9y agoRight. That's the entirety of their moat, plus brand recognition. What would Google have to spend to overcome that?