News for hackers. Stuff that matters.
Re:Docker 1.11: The first OCI-compliant runtime, built on co... by sengork on Wednesday April 13, 2016 @08:10PM (#11493398)
Standardisation at the format level will help with portability across different platform implementations.
Re:Docker 1.11: The first OCI-compliant runtime, built on co... by wmf on Wednesday April 13, 2016 @08:37PM (#11493515)
This "standardization" is pretty kludgey if you have to docker pull then docker export.
Re:Docker 1.11: The first OCI-compliant runtime, built on co... by alex1 on Wednesday April 13, 2016 @09:32PM (#11493724)
I think that's because OCI currently only has a specification for the runtime, not the distributable image. But it seems like as of a few weeks ago, work is underway to standardize the distributable image as well: https://github.com/opencontainers/image-spec
Re:Docker 1.11: The first OCI-compliant runtime, built on co... by kalmar on Thursday April 14, 2016 @12:53AM (#11494378)
I was almost excited! From the FAQ on the project you linked [0]:

> Q: Why doesn't this project mention distribution?

> A: Distribution, for example using HTTP as both Docker v2.2 and AppC do today, is currently out of scope on the OCI Scope Table. There has been some discussion on the TOB mailing list to make distribution an optional layer but this topic is a work in progress.

I really hope CoreOS manage to get distribution into the scope for OCI. We need to move beyond Docker images. Standardizing on-disk layout in OCI is only mildly useful in my opinion.

[0] https://github.com/opencontainers/image-spec#faq

Re:Docker 1.11: The first OCI-compliant runtime, built on co... by ibotty on Thursday April 14, 2016 @02:09AM (#11494619)
There are other tools that can get data from a docker v2 registry.
Re:Docker 1.11: The first OCI-compliant runtime, built on co... by jamescun on Thursday April 14, 2016 @05:06AM (#11495198)
It is standardisation of the file describing what parameters were used to build a container, ultimately every "implementation" has been a tarball of a linux filesystem which is usable with any linux container system (and possibly soon Windows).