TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Celebrating the Open Container Initiative Image Specification

71 点作者 polvi大约 9 年前

5 条评论

codehusker大约 9 年前
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 未加载
timthelion大约 9 年前
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 未加载
bkeroack大约 9 年前
I thought that&#x27;s what AppC was supposed to be? Does that mean AppC is moribund?
评论 #11499611 未加载
shockzzz大约 9 年前
If only Blue Origin &amp; SpaceX can behave this way too...
shockzzz大约 9 年前
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 未加载