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

科技回声

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

GitHubTwitter

首页

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

资源链接

HackerNews API原版 HackerNewsNext.js

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

Quark – A secure container runtime with CRI/OCI interface

24 点作者 andutu超过 1 年前

2 条评论

BobbyTables2超过 1 年前
Is there any real point to this?<p>Is this effectively anything more than a syscall filtered container?<p>To me, relaying syscalls from a guest in a VM to a host sounds like it is defeating the whole point of the VM!<p>At least normally a VM doesn’t have direct access to host syscalls — it is confirmed to the emulated block and network devices which (should) provide a constrained means of access.<p>Container escapes often happen because of exposure to host kernel interfaces (via syscalls!), and kernel file systems such as &#x2F;sys and &#x2F;proc (especially &#x2F;proc&#x2F;self shenanigans).<p>I fear they have reinvented a container, much less efficiently.
kjok大约 1 年前
Very cool! Curious to know the use cases for this tech?