Open Container Initiative specifications are 1.0

Re:Open Container Initiative specifications are 1.0 by cyphar on Wednesday July 19, 2017 @02:22PM (#14806588)

While this is somewhat true for the image-spec (with some very notable exceptions where the semantics have deviated heavily), it's absolutely untrue for the runtime-spec. As one of the people who maintains the legacy of what Docker did before the OCI (libcontainer which is now part of runc), the interfaces and semantics are very significantly different.

Docker does use the OCI runtime-spec internally now (with plans to support the image-spec at some point), but that happened after the spec had become fairly stable.

The most important thing is not where the spec design came from, but that it's now being maintained by a community that will make sure you don't end up with fragmentation and lock-in.

[ Parent | on HN ]

Re:Open Container Initiative specifications are 1.0 by pcthrowaway on Wednesday July 19, 2017 @09:11PM (#14809345)

How much does the OCI image spec differ from the one developed by CoreOS for appc? When OCI was announced, image spec was outside of its scope (https://coreos.com/blog/making-sense-of-standards.html), so coreos's work in this space seemed highly important. So has all work essentially been abandoned? Or did it inform the image spec of OCI (and 'what docker does') at all?

[ Parent | on HN ]