from Hacker News

Celebrating the Open Container Initiative Image Specification

by polvi on 4/14/16, 5:20 PM with 18 comments

• by codehusker on 4/14/16, 6:03 PM

  CoreOS has done a lot of work to avoid a monoculture of Docker containers, and I think we all benefit from the interchangeability of different implementations/runtimes.

  The future of containers just keeps getting brighter and brighter.

• by timthelion on 4/14/16, 8:22 PM

  Wait, they don't use hashes? Why???

      Image ID
          Each layer is given an ID upon its creation. It is     represented as a hexadecimal encoding of 256 bits, e.g., a9561eb1b190625c9adb5a9513e72c4dedafc1cb2d4c5236c9a6957ec7dfd5a9. Image IDs should be sufficiently random so as to be  globally unique. 32 bytes read from /dev/urandom is sufficient for all practical purposes. Alternatively, an image ID may be derived as a cryptographic hash of image contents as the result is considered indistinguishable from random. The choice is left up to implementors.

• by bkeroack on 4/14/16, 6:54 PM

  I thought that's what AppC was supposed to be? Does that mean AppC is moribund?

• by shockzzz on 4/14/16, 9:07 PM

  If only Blue Origin & SpaceX can behave this way too...

• by shockzzz on 4/14/16, 9:05 PM

  Weren't containers supposed to solve the whole "one interface for everything" nonsense? Now we have a standard interface for the standard interface?