kern-sandbox 0.1.30 → 0.1.32

package/README.md

@@ -33,8 +33,14 @@ import { runCode, withSandbox, Sandbox } from "kern-sandbox";
 npm install kern-sandbox
 ```
 
-You also need the `kern` binary on `PATH` (or point `$KERN_BIN` at it). Build it on Linux (no
-prebuilt binaries are published yet):
+You also need the `kern` binary on `PATH` (or point `$KERN_BIN` at it). The quickest route is the
+released static binary, whose checksum the script verifies:
+
+```sh
+curl -fsSL https://raw.githubusercontent.com/getkern/kern/main/install.sh | sh
+```
+
+From source instead, if you would rather not trust a published artifact:
 
 ```sh
 cargo install --git https://github.com/getkern/kern getkern --locked
@@ -43,6 +49,12 @@ cargo install --git https://github.com/getkern/kern getkern --locked
 kern needs a Linux kernel with unprivileged user namespaces + cgroup v2. On Windows it runs under WSL2.
 Node 18+.
 
+**On a Mac this package installs but cannot run**, and it says so rather than sending you after a
+download that does not exist: kern is Linux-only, because macOS has no namespaces and no cgroups. Run
+inside a Linux VM (colima, Lima, OrbStack, UTM), install `kern` and this package there, and it behaves
+as on Linux. Verified on Apple Silicon with an Ubuntu 24.04 guest.
+[Install notes for macOS](https://github.com/getkern/kern/blob/main/docs/INSTALL.md).
+
 ## A session: files persist, processes are ephemeral
 
 File state lives in a workspace directory on the host, bind-mounted into every box. Each `runCode`/`run`

package/index.js

@@ -36,7 +36,7 @@ const crypto = require("crypto");
 const zlib = require("zlib");
 const { spawn, spawnSync } = require("child_process");
 
-const VERSION = "0.1.29";
+const VERSION = "0.1.32";
 
 const DEFAULT_IMAGE = "python:3.12-slim";
 const WORKSPACE = "/workspace"; // where the persistent workspace is mounted inside every box
@@ -499,6 +499,16 @@ function findKern() {
       }
     }
   }
+  // On macOS the generic "install it" is a dead end: there is no macOS build to install. kern needs
+  // a Linux kernel, so the answer is a VM, and the error says which one rather than leaving the
+  // reader hunting for a download that does not exist.
+  if (process.platform === "darwin")
+    throw new SandboxError(
+      "the `kern` binary was not found on PATH, and this is macOS: kern is Linux-only " +
+        "(no namespaces, no cgroups on a Mac), so there is no macOS build to find. " +
+        "Run inside a Linux VM (colima, Lima, OrbStack, UTM), where kern installs normally, " +
+        "or set $KERN_BIN to a kern reachable from here. https://github.com/getkern/kern",
+    );
   throw new SandboxError(
     "the `kern` binary was not found on PATH - install it " +
       "(https://github.com/getkern/kern) or set $KERN_BIN",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "kern-sandbox",
-  "version": "0.1.30",
+  "version": "0.1.32",
   "description": "kern is a fast, rootless sandbox and virtual resource runtime for any workload, including untrusted and AI-generated code; kern-sandbox is its Node/TypeScript binding. Run untrusted or agent-generated code (Python/JS/Bash) in a real, kernel-enforced box in single-digit milliseconds, with no cloud, no account and no VM.",
   "keywords": [
     "sandbox",