Hacker News Reader

Comment by alex- | Hacker News Reader

I was introduced to linux cgroups and namespaces via my use of docker. It is a fantastic tool for using these concepts quickly and I don't currently see rocket etc overthrowing dockers dominance in the market place.

However I do sense (and feel my self at times) a growing upset with the usability/ stability of the docker engine.

The OCI (Open Container Initiative) should allow new solutions to come to market without fragmenting the space. i.e. it should be possible to run any image with any container engine/Linux.

Docker is valued at $1B. It appears that justifying that valuation has taken them into a number of adjacent markets. I wish they were more focused on the Docker Engine itself.

View on HN

Yep, the OCI is doing great stuff. At the bottom of the Cloud Foundry stack we have Garden-Runc (https://github.com/cloudfoundry/garden-runc-release). In past we had our own homegrown containerization technology and we're super happy to have been able to swap that out entirely in place of runc - it allows us to make use of the significant engineering talent contributed and has enabled us to move faster and reduce risk.

We're also buying into the image-spec for this reason.

Right now the focus is in underpinning CF, so although it is production ready functionally, it lacks the pretty fantastic user experience that Docker brings. Perhaps allowing us to reduce our focus on the containerizer, we'll be able to spend more time improving UX - which would be neat.

I believe the Kubernetes team is working on a simple implementation of the Kube API which is a thin wrapper around runc as well - so you're right, there are some cool things coming around as a result of the OCI.

> Yep, the OCI is doing great stuff. At the bottom of the Cloud Foundry stack we have Garden-Runc (https://github.com/cloudfoundry/garden-runc-release). In past we had our own homegrown containerization technology and we're super happy to have been able to swap that out entirely in place of runc - it allows us to make use of the significant engineering talent contributed and has enabled us to move faster and reduce risk.

Hi! I'm one of the maintainers of runC and I wanted to say that the CF stuff around runC is awesome. Keep it up. :D

> I believe the Kubernetes team is working on a simple implementation of the Kube API which is a thin wrapper around runc as well - so you're right, there are some cool things coming around as a result of the OCI.

Actually, ocid is mostly being worked on by people from the OCI community (runcom, mrunalp, myself and others). Though we are getting support from the Kubernetes folks with it, which is pretty cool. :D

Sweet. runC is awesome and using it is awesome. We are also super excited about the rootless work you personally have been doing, so thanks for your hard work in that area.

I can't take all the credit, Jess Frazelle was the reason that I started to work on an upstream version of binctr. But one of the cool things we can do with the rootless containers work (aside from making the lives of researchers easier -- something I've experienced personally) is to add OCI image building to KIWI (which is (open)SUSE's image building tool) and thus add it to OBS (the Open Build Service which is (open)SUSE's package building tool). I think there's a lot of cool things that will come out of rootless containers. :D

I'm going to be giving a talk about rootless containers at Linux.conf.au 2017 in case anyone is going to be attending.

That's the main issue with Docker right now. They've built an amazing static compiler that works with any language, but there's a question as to whether that compiler is worth 1B.

Reply on news.ycombinator.com