- 72comments
- 35comments
- 174comments
- 55comments
- 121comments
- 47comments
- 75comments
- 10comments
- 3comments
- 484comments
- 26comments
- 48comments
- 33comments
- 13comments
- 78comments
- 218comments
- 87comments
- 5comments
- 80comments
- 4comments
- 821comments
- 233comments
- 4comments
- 7comments
- 64comments
- 340comments
- 10comments
- 18comments
- 7comments
- 40comments
How does this compare to distrobox?
Distrobox mounts $HOME in the container at $HOME by default. WSL and NSL do not, and that's my preference. This means you can install tools that change your default path, change your dotfiles, etc, without affecting the host. The other obvious difference is that distrobox is powered by podman or docker, while NSL uses a VM that runs systemd-nspawn containers.
IS it LXC containers or docker? Or are you running a custom chroot namespace setup?
Haven't checked the actual project but he does state he uses systemd-nspawn. Which is it's own kind of container runtime.
He runs a systemd-nspawnd container in a "small vm", so neither really?
none of the above. a single vm started by systemd-vmspawn which then starts one or more containers for your instances using systemd-nspawn. It ends up being fast and lightweight.
The project is cool, but please use human written text.
The website's Claudisms are unbearable.
This is most useful to people who run Linux as their daily driver so rather than saying its like WSL can you explain what it offers that existing Linux containers do not?
Its also sounds different from WSL which I thought is a VM rather than a container.
Something that also require a bit of explanation. What do you do that makes this such a common problem.
WSL2 uses a shared VM that does host integration (networking, shared files, permanent storage for each instance). NSL uses the same model but with Linux native technical implementations.
As for keeping my host clean - it's the developer's curse that always gets me. Install libWhatever3.2-dev because you need it to compile something, then don't realize until next time you open Chrome that it broke your system in some subtle way. There are dozens of ways to solve this like devcontainers, docker, incus, fully separate or remote vms. I like the WSL2 model so I wanted that same UX.
So you've just basically reimplemented LXC?
Nope. This is a VM, with containers inside. And the containers weren't "re-implemented", it uses existing systemd containers. That's what I was able to learn by skimming the site for 30 seconds. Did you not even do that? And why even be so condescending to someone else's project?
Because it does seem like we already have tools that skin this particular cat, it's valid to wonder what value this project provides over existing solutions.. even if they chose the wrong example to compare it to. Why do you think that's condescending?
LXC is a jail and qemu is an extra layer of emulation. Why pay that extra cost? Just because it serves a wsl image isn't really an answer. How is that worth the extra layer? See, no answers worth reading in your response.
Yeah, I can see you don't read much, so would miss something like that. Understand the difference in isolation levels between containerization and virtualization, what "emulation" is, then come back... oh, nevermind. I already lost you.
Yep, no idea what namespaces and cgroups are. Haven't been using linux since 25 years. And don't know what virtualization means, either. But maybe someone as superior as you would enlighten us.
There's already Distrobox, which does exactly the same thing but isn't slop.
I have to say this is nice packaging. It is weirdly not obvious how nice it is to cleanly use a different “machine” inside your desktop.
I never thought I’d prefer WSL to even my MacBook for working with remote servers and dev but somehow I do.
I of course know the many ways to roll something like this for myself, yes dev containers are better for many things etc. but it’s wierd how good the ergonomics of a WSL like container are.
Thanks for saying so! That's exactly why I wrote this. The UX of wsl2 is just right. There are a lot of other ways to accomplish this, but none touch that same experience.
Looks very cool.
Now all you have to do is run NSL under WSL.
challenge accepted!
I'm confused why VM + systemd-nspawn? From my understaing WSL 2 runs a single VM + something like systemd-nspawn per "linux installation", but it runs a VM because it needs linux kernel. Why not just do systemd-nspawn if you alread on linux?
Claude told him to do it this way.
I'd trust OP to make good architectural decisions/provide guidance even if AI mostly wrote the docs and UI. Looking into their GitHub, seems they are an engineering manager at Microsoft and contribute semi regularly to uBlue and Project Bluefin. Should be better quality than some random vibeslopper.
you could, and if that's your preference https://nspawn.org is just right.
Neat, I wasn't aware of this tool. I just either run nixosContainer in systemd-nspawn or OCI image in systemd-nspawn.
Way better isolation, is my guess. Plus, you can use a different kernel this way.
I used to poo-poo when people said that containers aren't a _real_ security boundary, at least for personal stuff, and not a multi-tenant server. But I bet even mid-tier LLMs can break out of LXC/Docker/nspawn at this point.