NixOS-WSL VS home-manager

I have not used it but this might be what you are looking for: https://github.com/nix-community/NixOS-WSL

You could also install the nix package manager on Ubuntu.

This project began as I didn't like that NixOS-WSL used systemd in the background, so I made this for myself. Some of the advantages: faster boot time, smaller image size and a FHS distro in the background, that lets you load dynamically linked binaries (for example, to have VSCode remote working OOTB).

There's a community port of NixOS to WSL2, complete with systemd support, plus Docker Desktop support and some other goodies: https://github.com/nix-community/NixOS-WSL

Nix also works on other WSL distros, provided they're using WSL2.

Nix supports cross-compiling Windows binaries as well. I know some people use it for that.

There is no 'native' support— you can't use Nix as an alternative to Winget or Chocolatey on Windows. Right now a lot of important stuff in Nixpkgs depends on a POSIX shell and Unix coreutils implementation for the basic build environment, and that's shared between many operating systems. Trying to fit Windows into that doesn't really make s sense, and there's not really any momentum behind the idea of using any particular other runtime environment (could be a scripting language instead of a shell + coreutils) for those basic builders.

But it's conceivable that some day, one or more companies using Nix on WSL might see vaiue in taking that extra step and put together a Nix-based package collection for Windows and help get the Nix Windows port out the door.

Basically, I managed to get NixOS inside WSL2 by using this: https://github.com/Trundle/NixOS-WSL

But whenever I try running code . with nixos-wsl(https://github.com/Trundle/NixOS-WSL), the error: `code: command not found` is thrown, also, whenever I try to open nixos-wsl from vscode, it does not work and the terminal throws a bunch of errors?

I really am at lost rn, foud this github issue tried the solution and it didn't work.

{ config, pkgs, ... }: { imports = [ (import "${builtins.fetchTarball https://github.com/rycee/home-manager/archive/master.tar.gz}/nixos") ]; users.users = { jdoe = { isNormalUser = true; initialPassword = "1234"; extraGroups = [ "wheel" ]; }; }; home-manager.useUserPackages = true; home-manager.users.jdoe = { home.stateVersion = "21.11"; programs.home-manager.enable = true; programs.git.userName = "John"; programs.git.userEmail = "Doe"; programs.zsh.zplug = { enable = true; plugins = [ { name = "zsh-users/zsh-autosuggestions"; } { name = "romkatv/powerlevel10k"; tags = [ as:theme depth:1 ]; } { name = "ohmyzsh/ohmyzsh oh-my-zsh"; } { name = "ajeetdsouza/zoxide"; } { name = "marlonrichert/zsh-autocomplete"; } { name = "marlonrichert/zsh-edit"; } { name = "zsh-users/zsh-autosuggestions"; } { name = "ptavares/zsh-exa"; } { name = "zsh-users/zsh-syntax-highlighting"; } { name = "mbenford/zsh-tmux-auto-title"; } { name = "zsh-users/zsh-history-substring-search"; } ]; }; services.gpg-agent = { enable = true; defaultCacheTtl = 1800; enableSshSupport = true; }; }; }

There are multiple ways of managing declarative profiles. 1) Attrset, compatible with imperative use of nix-env https://git.io/fAQHW ; 2) buildEnv, providing more control over the paths that are linked into the profile https://git.io/fp0aU ; 3) home-manager, providing nixos-like config for your ~ https://github.com/rycee/home-manager