guest: give hermes-install a broader PATH (fixes sh: command not found)

hermesInstallDeps had no package providing a bare `sh` - the upstream
installer's uv-install step invokes it via PATH lookup, not /bin/sh, and
NixOS systemd units only get a `path`'s explicit packages. bash's own bin/
ships an sh -> bash symlink, confirmed against the exact store path from
the failing unit's log. Also adds a broader coreutils-adjacent baseline
(tar, gzip, which, grep, sed, awk, find) so the next installer that shells
out to a common tool by bare name doesn't cost another rebuild cycle.
This commit is contained in:
ari committed 2026-09-16 11:09:28 -04:00
1 parent 04d1889101
commit f1456b66e5
1 file changed
+9 -3
+9 -3
View File
@@ -32,14 +32,20 @@ let
# propagate into systemd services' PATH on its own - a bare `curl` inside
# a systemd script only resolves if the unit is explicitly given a `path`,
# which is what actually failed here (confirmed live: "curl: command not
# found" from inside hermes-install, despite curl being in
# systemPackages). The installer also shells out to git/node/python/gcc
# internally, so the service needs all of this, not just curl.
# found", then separately "sh: command not found" from the upstream
# installer's uv-install step, both from inside hermes-install despite the
# tools existing in systemPackages). `bash` is included explicitly because
# its output provides `bin/sh` (the same symlink NixOS's own `/bin/sh`
# compat path points at) - nothing else in this list provides a bare `sh`.
# The rest of the coreutils-adjacent tools are a baseline so the next
# third-party install script that shells out to some common Unix tool by
# bare name doesn't trigger another one of these round-trips.
hermesInstallDeps = with pkgs; [
git curl jq ripgrep fd tree htop
uv nodejs ffmpeg
direnv nix-direnv nix-output-monitor
gcc gnumake pkg-config python3 xz
bash coreutils gnutar gzip which gnugrep gnused gawk findutils
];
in
{