TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Celebrating the Open Container Initiative Image Specification

71 pointsby polviabout 9 years ago

5 comments

codehuskerabout 9 years ago
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&#x2F;runtimes.<p>The future of containers just keeps getting brighter and brighter.
评论 #11500580 未加载
timthelionabout 9 years ago
Wait, they don&#x27;t use hashes? Why???<p><pre><code> 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 &#x2F;dev&#x2F;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.</code></pre>
评论 #11500254 未加载
bkeroackabout 9 years ago
I thought that&#x27;s what AppC was supposed to be? Does that mean AppC is moribund?
评论 #11499611 未加载
shockzzzabout 9 years ago
If only Blue Origin &amp; SpaceX can behave this way too...
shockzzzabout 9 years ago
Weren&#x27;t containers supposed to solve the whole &quot;one interface for everything&quot; nonsense? Now we have a standard interface for the standard interface?
评论 #11500459 未加载