News for hackers. Stuff that matters.
Re:RunC – A lightweight universal runtime container, by the ... by toomuchtodo on Monday June 22, 2015 @03:07PM (#9760503)
> Now what we're seeing is a runtime for this binary being ported around to different platforms. This could get interesting.

With x86 being the primary server/workstation workhorse (lets exclude mobile platforms for the moment), is all of this abstraction necessary? Doing Infrastructure and DevOps, I definitely see the benefit of containerization for build reproducibility and decreasing the friction developers face for running applications locally as they run in production.

Not everyone needs Borg/Mesos/Mesosphere. Not everyone needs containerization. When you have a hammer though, everything starts looking like a nail.

Re:RunC – A lightweight universal runtime container, by the ... by alexchamberlain on Monday June 22, 2015 @03:32PM (#9760654)
I bet they all use HTTP to communicate too... Seriously though, I tend to agree, could this be solved by using more static binaries?
Re:RunC – A lightweight universal runtime container, by the ... by XorNot on Tuesday June 23, 2015 @04:44AM (#9763367)
A return to statically linkable glibc would be a good start on that. It's definitely the weakest link in the chain (as in, the only thing which a pulled in cgo dependency tends to start complaining about).
Re:RunC – A lightweight universal runtime container, by the ... by felixrabe on Tuesday June 23, 2015 @03:36AM (#9763138)
It could, but there are many existing technologies (apps, libraries, languages) that are easier (and more consistently) turned into a container than into a static binary.