News for hackers. Stuff that matters.
Re:RunC – A lightweight universal runtime container, by the ... by api on Monday June 22, 2015 @02:10PM (#9760145)
What we're seeing emerge here is a new universal binary format.

I've thought of Docker containers for a long time as gigantic statically linked binaries. This isn't necessarily a bad thing (though it does present issues). In some ways the process of installing the different moving pieces of a service and configuring them is a bit like manually "linking" something -- sub-services like MySQL, Redis, etc. are analogous to libraries.

Now what we're seeing is a runtime for this binary being ported around to different platforms. This could get interesting.

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.
Re:RunC – A lightweight universal runtime container, by the ... by vezzy-fnord on Monday June 22, 2015 @02:26PM (#9760232)
What we're seeing emerge here is a new universal binary format.

Insofar as libcontainer can ram as many ways to implement OS-level virtualization across platforms, that is.

Re:RunC – A lightweight universal runtime container, by the ... by pron on Monday June 22, 2015 @11:40PM (#9762484)
Containers won't run across different OSes (Linux/Windows) without VM virtualization. The spec doesn't actually cover the executable binary format. In the end, a container process is just a native process of the host operating system that is isolated from other processes. There is no OS virtualization taking place.
Re:RunC – A lightweight universal runtime container, by the ... by SEJeff on Sunday June 28, 2015 @12:09PM (#9793984)
That entirely depends on your definition of "virtualization". I for one would completely consider all of the namespace support that docker/rkt/lxc use to be virtualization. The reason being since the container has a different pid/network/mount namespace from the host, it is a "virtualized" version thereof.

Now clearly this is different than traditional full operating system virtualization ala KVM/Xen, but it is absolutely still a form of virtualization. Just because something is different doesn't make it wrong.

Re:RunC – A lightweight universal runtime container, by the ... by kraig on Monday June 22, 2015 @05:38PM (#9761387)
it's effectively what apple has been doing in OSX with .app