Relationships
#4893 Ship a linux-riscv64 binary (enables real swamp in the browser via unkernel)
Opened by sntxrr · 11/18/2026
Problem
swamp ships binaries for darwin-aarch64, darwin-x86_64, linux-aarch64, linux-x86_64 and windows-x86_64 only (checked against release v20261118.223849.0-sha.c2530f0f). There is no linux-riscv64 build, so swamp cannot run on RISC-V Linux at all.
The concrete use case: an in-browser swamp getting-started running real swamp, not a simulation, inside unkernel. unkernel is the real Linux kernel compiled to WebAssembly, running unmodified riscv64 Alpine/Ubuntu userland in any modern browser (and in Node/Deno). It boots to a shell in well under a second. Measured from a swamp extension that boots it in-process, guest boot takes about 30-40 ms and a full /bin/sh -c run takes about 200 ms. A new user could open a page and get a working Linux shell with swamp installed: swamp repo init, create a behavior, run it, query data. There would be nothing to install and no server.
riscv64 is the only user-space architecture unkernel runs, so that's the blocker.
What exists today
- Deno has no official riscv64 release either; v2.9.8 assets are x86_64 and aarch64 only.
- Alpine riscv64 (edge and 3.24) has Node 24 and 26 but no
denopackage. - Arch Linux RISC-V does ship a community build,
deno-2.9.8-1.1-riscv64(glibc). That's the same Deno version swamp currently bundles, which suggests the toolchain path exists.
Proposed solution
Publish a swamp-linux-riscv64 release asset, built against a riscv64 Deno/denort. Either:
- cross-compile Deno/denort for
riscv64gc-unknown-linux-gnu(the route the Arch RISC-V package takes), or - track upstream Deno if or when it adds riscv64 to its release matrix.
A musl or static build would be ideal for Alpine. glibc is still usable on Alpine via gcompat or by bundling the loader.
Alternatives considered
- Run swamp on a host and only use unkernel as a sandbox for steps. This works today: we built a behavior that runs commands in a throwaway unkernel guest with network off and read-only mounts by default. But it isn't swamp-in-the-browser.
- Use the community Arch riscv64 Deno to run swamp from source in the guest. This is unofficial and unverified, and performance under a riscv64 JIT inside wasm is unknown. It's useful as a feasibility spike, but not something to ship to new users.
Open
No activity in this phase yet.
Sign in to post a ripple.