macOS: one Linux microVM per box on Virtualization.framework

Open
#48 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
12/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
rust, wasm

Research direction

This is a design-heavy feature: a macOS launcher on Virtualization.framework (via objc2-virtualization or libkrun) behind the sandbox and placement interfaces. Start by reading the existing sandbox and placement interface definitions in the Rust crates and the vsock-related forwarders in wicket-entry, which the issue says must move from unix sockets to vsock. Done means a box boots in under about 2 s on Apple silicon with no network except wicket's proxies and passes the acceptance flows; the research notes in 02 §4.3 and §4.6 and issue #37 should be read first.

Written by the indexing model from the issue text.

Description

enhancement parked

Why. A native Mac backend with isolation stronger than gVisor (each box gets its own kernel), running the same Linux images.

What.

  • A small launcher on Apple's Virtualization.framework (from Rust via objc2-virtualization, or libkrun on Apple's hypervisor), behind the sandbox and placement interfaces.
  • Each box is a minimal arm64 Linux VM:
    • root filesystem from the OCI image;
    • virtiofs shares for workspace, state and volumes;
    • no network device;
    • wicket's proxies reached over vsock: wicket-entry's forwarders connect over vsock instead of to unix sockets, and the host side bridges each vsock port to the run's sockets.
  • If libkrun: its feature that performs guest network calls on the host (TSI) must be off, and the VMM itself confined.
  • Save and restore of machine state (macOS 14+) can back parking later (#8, #29).
  • Isolation tier vm, ranked above gvisor by the subset rule.

Done when. A box starts in under ~2 s on Apple silicon, has no network but wicket's, and passes the acceptance flows.

Refs. research 02 §4.3, §4.6; #37.

Dominant language
Rust
Stars
0
Forks
0
Avg merge
1h 43m
Merged PRs (30d)
190

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from public/wicket

All issues in public/wicket

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.