Need help?
<- Back

Comments (68)

  • rao-v
    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.
  • 0x457
    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?
  • dathinab
    How does it differ from existing tools kinda do exactly same, like e.g. toolbx. (And to a slightly lesser degree flatpack, snap, etc.)?And what prevented adopting/supporting existing projects, instead of further tool ecosystem fragmentation? (kinda the same question, just differently phrased)
  • thayne
    How does this compare to distrobox?
  • aj2048
    I've wanted a little more isolation than what distrobox can give me for a while now, and I did enjoy WSL when I used Windows. I've also never heard of Frostyard before, and the other repos look pretty interesting as well. Thanks for sharing!
  • graemep
    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.> It's yet another step in my long journey to keep my host installation free from all the changing and breaking dev dependencies that force a reinstall every few months.Something that also require a bit of explanation. What do you do that makes this such a common problem.
  • rpcope1
    So you've just basically reimplemented LXC?
  • Fnoord
    'National security letter' for Linux?I think I'll stick to Nix & Podman.
  • bita_nidir
    I'll give this one a try, thanks for sharing!FWIW, I'm currently using systemd-nspawn via mkosi: https://github.com/systemd/mkosiIt makes an image and runs it in separate namespace. It can start at bash or init. It's very fast but there seem to be a problem creating an Ubuntu image on Debian and vice versa.
  • naman_307
    Is the VM layer mostly for host hygiene, or are you also treating the instances as a real security boundary when something untrusted (deps or agent-written code) runs inside?
  • michaelastreiko
    Nice flip of the WSL idea the other way — simple interop like this keeps a one-person stack from turning into a VM zoo.
  • teeskay
    Just a recommendation that difference between docker container and nsl on homepage is worth it
  • dingaling911
    Looks very cool.Now all you have to do is run NSL under WSL.
  • bee_rider
    The name WSL has always struck me as a bit back area (LSW would seem to make more sense, since it is a Linux subsystem for Windows). I guess they mean it as a Windows Subsystem for Linuxing.Anyway, should this be called LSL or WSLL? Or maybe LSWSL.
  • 28304283409234
    Always looking for a successor to https://developer.hashicorp.com/vagrant. Is this it?
  • anon
    undefined
  • frunklooper
    Nobody wants this
  • bezko
    someone has to ask the question: can you run lsl in wsl?
  • senectus1
    would really like a NixOS for this. would be interesting to play with and figure out.
  • RandomGerm4n
    There's already Distrobox, which does exactly the same thing but isn't slop.
  • codr1
    This is very cool. GG.
  • varispeed
    The project is cool, but please use human written text.The website's Claudisms are unbearable.
  • the_real_cher
    IS it LXC containers or docker? Or are you running a custom chroot namespace setup?