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.

Quark – A secure container runtime with CRI/OCI interface

24 pointsby andutuover 1 year ago

2 comments

BobbyTables2over 1 year ago
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.
kjokover 1 year ago
Very cool! Curious to know the use cases for this tech?