nix-index VS miniguest

nix-index can be used to provide this functionality, and to automate this process you can use nix-index-database (setup instructions are in the README).

Are you using flakes? AFAIK `command-not-found` does not work with them. See https://github.com/NixOS/nixpkgs/issues/171054 and https://discourse.nixos.org/t/why-isnt-there-an-official-bui...

I think `nix-index` works as a replacement: https://github.com/bennofs/nix-index

If you are on another distro or mac os there is also nix-index

nix-index is another option for searching for pkgs. You can search by name, or by specific files within a pkg.

You can use nix-locate from https://github.com/bennofs/nix-index to find files on NixOS:

nix-index makes it trivial to find which package contains a given file.

There are two ways I know of: - If you use old-school channels, there's an index in the channel. In particular, the command-not-found hook is able to use that. In this particular case, you would have to guess that git will look for the git-clang-tools, and command-not-found that. This looks like it only works for programs, not arbitrary files. - In any case, you can use the more general nix-index. That's what I did because I use flakes.

I use nix-index a lot to find which derivation a file belongs to, but building the index takes a while and so I end up not updating it very frequently.

Look at the library missing say X Use nix-locate to find the derivation that includes libX.dylib file (if it can’t find the macOS dylib version of the file try using the same name for linux by changing dylib for so) Add the derivation to you environmental and try again It will find the next missing library on the next compile.

I got a hook like that working recently, but it was with devshell.

Not all containers are Docker. Docker containers are so-called application containers with no init daemon. NixOS modules rely on an init daemon (systemd) to start services, so if you're looking at NixOS, trying to contort it into an application container might not be the easiest way to go about this. There's also no official NixOS docker template. (There's a Nix package manager one but I don't think that's what you want, I don't think it has systemd) What I'm suggesting is more of a LXC-style operating system container that starts NixOS at stage 2. As for how to go about it, This article presents a straight-forward looking solution. Alternatively, you could have the guest share the host's nix-store with miniguest (shameless self-promotion)