Experiment: gVisor inside Kiri's VM for macOS nodes; Kiri as prior art

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
15/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
docker, linux, macos, rust

Research direction

The work is an experiment on an Apple silicon Mac running Kiri's Linux VM, not a code change in wicket. Start by installing Kiri and checking whether gVisor's systrap platform runs in its guest kernel, then record the kernel config gaps. The documentation step is to add a Kiri entry to docs/explanation/prior-art.md. Done means a recorded yes or no on step 1, timing numbers for step 2, and the new prior-art section.

Written by the indexing model from the issue text.

Description

Kiri (Apache-2.0, Rust, created 2026-11-02) is a Docker-Desktop replacement. On macOS it runs one small Linux VM (Virtualization.framework, a 10 MB allnoconfig kernel, a ~900 KB Rust PID 1 controlled over vsock). It starts containers with one clone3 into namespaces and the cgroup (CLONE_INTO_CGROUP), with no runc, shim or dockerd, and serves the Docker Engine API. On Linux it runs on the host kernel.

For wicket. Its containers share a kernel, so on Linux it is a runc-like tier, below gVisor, and it has no pluggable runtime: wicket's --runtime runsc doesn't apply. It matters as:

  • a light Docker-API host for macOS nodes (#47), and a reference for the one-VM-per-host designs (#64 Firecracker, #48 Virtualization.framework);
  • a source of speed ideas: no per-container helper processes, cgroup placement at clone, netlink and nf_tables written directly.

Experiment.

  1. Can gVisor's systrap platform (no KVM, no ptrace) run inside Kiri's guest VM, as a runtime wicket can start boxes with? What kernel config does it need that Kiri's allnoconfig kernel lacks?
  2. If yes, box start time and egress throughput there against gVisor on a Linux node; if no, what the runc tier on Kiri gives a Mac node, and what it doesn't.
  3. Add Kiri to docs/explanation/prior-art.md (what it is, what wicket takes from it, what it doesn't).

Run on a Mac (Apple silicon) with Kiri installed; nothing here needs to be built into wicket.

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.