4 ms·
ELI5 the OCI & why it's important? I follow Docker from a distance and find it fascinating.
by emdd 10y ago
ELI5 the OCI & why it's important? I follow Docker from a distance and find it fascinating.
- shykes 10y agoDisclaimer: I work at Docker. Docker has become a de facto standard for executing programs in a portable sandbox (aka "container"). There were increasing demands for making it a "proper" standard, so last year we donated a spec and reference implementation for a universal intermediary format - a "PDF of containers" if you will, and partnered with the Linux Foundation to manage it. The majority of the industry followed. Now that the Docker container engine supports this intermediary format, and other providers will soon follow suit, it reduces the risk of depending on one provider. If you want to switch away from Docker, you can run your containers elsewhere. Now everyone can focus on building better tools, instead of trying to make "their" format win. The result is better tools.
- skj 10y agoAs ELI5s go, this seems not well-targeted at 5-year-olds :)
- nindalf 10y agoAs is pointed out repeatedly on /r/ELI5, the explanation doesn't need to be for literal 5 year olds.
- emdd 10y agoCorrect. It's not literal, and I didn't mean it literally (I don't think anyone actually does). I would probably have not been happy if that was the only type of answer. Maybe, we will say ELI16? Kidding. No, don't do that.
- skj 10y agoI'm aware, but I felt like shykes was simply repeating the copy from the blog post without actually breaking it down into simpler pieces. A sibling post did much better.
- ysh7 10y agoDisclaimer didn't say you are the CEO. I hope this guy does this again here, https://news.ycombinator.com/item?id=11379475 https://news.ycombinator.com/item?id=11379475
- deleted 10y ago[deleted]
- molecule 10y ago> Disclaimer didn't say you are the CEO. Correction: not CEO, "Founder, CTO and Chief Product Officer" https://www.docker.com/company/management https://www.docker.com/company/management
- tlrobinson 10y agoSolomon's comment and disclaimer seemed perfectly reasonable to me. Why does it matter if he's the CTO or random employee?
- patrickg_zill 10y agoI am sorry if this comes across as mean-spirited, but, I think it is quite disingenuous to claim that Docker is a "de facto standard". OpenVZ for instance, has well over 77K host-nodes which run over 840K containers. These are not ephemeral setups on someone's laptop but servers that companies are spending money on each month to have in a datacenter. IMHO (because the reporting method requires a small stats program to run, which is optional and many don't run it) there are 2 to 10 times more in actual existence. Source: https://stats.openvz.org/ https://stats.openvz.org/
- vacri 10y ago'a' defacto standard, not 'the' defacto standard.
- shykes 10y agoYou don't come across as mean spirited, it's a fair point. I didn't mean that Docker is the most widely deployed software in a particular category (that would be hard to measure accurately anyway). But what Docker introduced is the use of containers to deliver software, not just boot servers. Developers use Docker to package and publish their runnable artifacts, in very large numbers. For example Docker Hub passed 2.5 billion image downloads. Many more images are certainly transferred between private nodes every day. OpenVZ does have a concept of templates (I was an avid user in past life) but they were never intended as a means to distribute applications. In that regard Docker is undisputably the de facto standard. I hope this clarifies my meaning. PS. OpenVZ is awesome. I remember when we made the switch from ovz to lxc in 2010, when it became clear which would get merged mainstream, and we could finally ditch our double-patched xen+ovz kernels. The transition was very painful! What we missed most was the "bean counters" feature, ovz stats were unmatched for quite some time.
- simula67 10y agoAm I correct in assuming that containers specified by OCI can be exported and managed by other tools like lmctfy. You see your competitive advantage being in docker.
- robszumski 10y agoAs an industry, we hadn't put down on paper what it means to build, execute or discover a container. If you wanted to sit down and write software to build or execute a container, there wasn't a spec to follow or a checklist of the features you needed to support. Basically, you had no idea if what you wrote today would continue to work in the future. Or if someone else constructed a container, that you could run it. (CoreOS employee)