You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[upstream pr #515] docs(512): propose a VM Sandbox backend (Sandboxes as namespaces in one VM per Store) #47
One Linux VM per Store. Inside it, the existing worker runs the SDK with the Store opened in-process on the VM's ext4 disk, which is today's Linux topology.
A namespace backend replaces Docker inside the VM:
each Sandbox gets its own mount, PID and IPC namespaces and a cgroup;
its daemon runs as root with /dev/fuse;
commands run as a nonroot uid:gid with no capabilities and no-new-privs.
It uses safe nix calls from one small helper binary, with no unsafe Rust and no util-linux.
Provider adapters in @layerfs/runtime. Each one creates the VM, attaches the Store disk, starts the worker and opens one private stream to it. The first candidates are Microsandbox and any Linux host over SSH, such as EC2.
Docker stays the default. The new backend is a second variant of a concrete Runtime enum.
Activity