TL;DR
Get the latest gadgets delivered free — and shop member deals
- Fast, free delivery on millions of items
- Access to Prime Big Deal Days deals on October 6–7
- Prime Video, Amazon Music and more included
A project called NSL, short for NSpawn Subsystem for Linux, was posted to Hacker News as a ‘Show HN’. It offers WSL-like persistent development machines on Linux: systemd-nspawn containers running in a shared VM, with weekly-rebuilt signed images of seven distributions. It is pre-release software (v0.4.0) tested on one host.
A developer project called NSL (NSpawn Subsystem for Linux) appeared on Hacker News this week via a Show HN post, offering a tool that brings the Windows Subsystem for Linux (WSL) workflow to Linux itself: disposable-feeling but persistent development machines that keep their packages, services and files between sessions, while the host system stays untouched. According to the project’s report at frostyard.github.io, the machines run as systemd-nspawn containers inside a shared virtual machine and are aimed primarily at developers using atomic Linux hosts, where installing packages directly is impractical.
The core pitch, per the project’s documentation, is that users can install development tools inside a Debian, Fedora or other Linux machine and leave the host alone — attractive on immutable or atomic distributions where the root filesystem is read-only by design. Creating a machine is a single command: nsl create debian –distro debian:13, after which running nsl from any project directory opens a login shell in the default machine, in that same directory. A nsl run make test invocation runs one command and returns its exit status to the host, mimicking WSL’s wsl.exe behavior.
Integration with the host goes beyond a plain container. The project says a user’s $HOME, /run/media/USER and /mnt are available inside the machine under /mnt/host, and the machine adopts the user’s username, UID and GID so files created from inside still belong to the host account. Passwordless sudo is provided inside the machine. Servers started in a machine expose forwarded ports on host 127.0.0.1, and Wayland applications can open windows on the desktop through Waypipe.
NSL ships with seven distributions — Debian, Ubuntu, Fedora, CentOS Stream, Arch, openSUSE Tumbleweed and openSUSE Leap — whose images are rebuilt weekly and, per the project, verified as coming from a signed Frostyard publishing workflow before use. An –isolated mode gives untrusted software its own VM with no access to host files, the desktop or host actions. Notably, nsl runs entirely as the user: it does not install packages or alter device permissions, groups or sudoers, though host prerequisites must be installed first.
Why WSL-Style Machines on Linux Matter
WSL is one of the most praised developer features on Windows precisely because it separates a mutable development environment from a stable host. Linux users on atomic/immutable distributions such as Fedora Silverblue, openSUSE MicroOS or Snow Linux have historically lacked an equivalent with the same convenience: Flatpak covers GUI apps, Toolboxes cover some workflows, but a WSL-like model with per-distro machines, port forwarding and GUI pass-through is a different proposition. NSL targets exactly that gap.
The design choice of running systemd-nspawn containers inside a shared VM also gives a middle ground between full VMs (heavier, slower to start) and bare containers on the host (weaker isolation). The project states machines start when needed and can work directly in host files, which addresses the most common complaint about VM-based dev environments — file access friction. If the tool matures, it could become a standard part of the atomic-desktop developer story, though that remains speculative at this stage.
From WSL to NSpawn: The Lineage
Microsoft’s WSL, first released in 2016 and rebuilt around actual Linux virtual machines in WSL 2, popularized the model of lightweight, persistent, per-distribution development environments tightly integrated with the host filesystem and network. Linux has several partial analogues: Toolbox and Distrobox provide containerized shells, systemd-nspawn provides container machinery, and qemu-based VMs provide isolation — but no widely adopted tool combined them in the WSL shape before projects like NSL attempted it.
According to the project’s report, NSL is a Frostyard effort and explicitly a pre-release: v0.4.0 is described as the first release of this design, while v0.3.0 and earlier were a retired prototype. The tested host is Snow Linux 13 on x86-64 with systemd 261.2, QEMU 10.0.13, virtiofsd 1.13.2 and GNOME Wayland — a narrow, specific environment that defines the project’s current support envelope.
“nsl works much like WSL: each machine keeps its packages, services and files between sessions.”
— NSL project documentation (frostyard.github.io)
Early-Release Caveats and Untested Hosts
The project itself states plainly that nsl has no stable release yet; v0.4.0 is the first release of the current design, and earlier versions are a retired prototype. Official testing covers only Snow Linux 13 on x86-64 with a specific stack (systemd 261.2, QEMU 10.0.13, virtiofsd 1.13.2, GNOME Wayland). Behavior on Fedora Silverblue, Ubuntu, Arch or other distributions is not documented in the source material and is not yet clear.
Performance characteristics — VM startup time, memory overhead of the shared VM, filesystem speed through virtiofs — are not quantified in the project’s report. The security model beyond the –isolated tier, including how host actions are mediated for non-isolated machines, is only briefly described. Community reception on Hacker News was ongoing at the time of writing, and it is not yet clear whether other developers have independently tested the tool.
Roadmap and Adoption Prospects
The immediate next steps, per the project’s own documentation structure, are its three entry points: a get-started guide, an architecture document explaining how the VM runs machines and connects them to the host, and a command reference covering commands, nsl.conf settings and published images. Continued weekly image rebuilds of the seven supported distributions are part of the ongoing publishing workflow.
For the project to move beyond pre-release status, it will need to demonstrate reliability beyond its single tested host, publish details on versioning and upgrade paths from v0.4.0, and — judging by the typical arc of Show HN projects — respond to community feedback from the Hacker News thread. Readers interested in trying it should follow the Frostyard site for a stable release before relying on it for production development environments.
Key Questions
What is NSL?
NSL (NSpawn Subsystem for Linux) is a developer tool that provides WSL-style persistent Linux development machines on a Linux host. According to the project, machines run as systemd-nspawn containers inside a shared VM, keep their state between sessions, and integrate with host files, ports and the Wayland desktop.
How is NSL different from Distrobox or Toolbox?
Toolbox and Distrobox run containers directly on the host with Podman/Docker. NSL, per its documentation, runs its containers inside a VM, adding a virtualization boundary, built-in port forwarding to 127.0.0.1, Waypipe GUI pass-through, and a dedicated –isolated mode with its own VM for untrusted software.
Is NSL stable enough for daily use?
No. The project states it has no stable release yet and that v0.4.0 is the first release of the current design, with v0.3.0 and earlier retired as a prototype. Only Snow Linux 13 on x86-64 is documented as tested.
Which distributions can I run inside NSL machines?
According to the project: Debian, Ubuntu, Fedora, CentOS Stream, Arch, openSUSE Tumbleweed and openSUSE Leap. Images are rebuilt weekly and verified against a signed Frostyard publishing workflow before use.
Does NSL require root or change my host system?
The project says nsl runs as your user and does not install packages or change device permissions, groups or sudoers. However, host prerequisites (such as QEMU and virtiofsd) must already be installed before it will work.
Source: hn
Evergreen bestsellers Picks
bestsellers
As an affiliate, we earn on qualifying purchases.
