Question: Thoughts on comparison to bubblewrap?
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 821
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
TinyKVM is very cool. I'm enjoying reading about it, and eager to play with it for various workload secure isolation use cases.
With it's minimal overhead, it reminds me very much of bubblewrap from a usage perspective (minimal overhead to launch a binary). I'm sure you're familiar with it, so I'm wondering how you think about TinyKVM and bubblewrap?
To me, they seem to accomplish similar goals, albeit TinyKVM can more easily be used in code rather than just calling bubblewrap as an executable. I'm sure there are some feature differences as well.
I'm surely not as familiar with virtualization as you, but it seems bubblewrap goes for a more "entire container limited in permissions", where as TinyKVM is more "just the binary"?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
This issue is an open comparison question about TinyKVM and bubblewrap, with no files, tests, or specific change identified. Start by reviewing the issue discussion and the project description; it would need a decided documentation scope and a clear definition of what comparison or explanation is considered complete.
Written by the indexing model from the issue text.
Assessment
- Domain
- operating-systems, security
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100