Fix proxmox remote build bootstrap

Conversation 0 Commits 2 Files Changed 2

+46 -1

2 Commits

Author	SHA1	Message	Date
beatzaplentyandClaude Sonnet 5	9a1d6842d7	Generalize the remote tooling check to a list of required commands Check NixOS configurations / eval-hosts (pull_request) Failing after 12m13s Details Per-run tooling verification (added in the previous commit) was hardcoded to checking just `nix`. Turn it into a small array instead, so a future remote build step needing another tool extends that list rather than growing a second parallel check. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-07-20 14:42:00 +00:00
beatzaplentyandClaude Sonnet 5	f5ef3194d4	Fix remote-build bootstrap: retry on partial failure, fix sudo-less root Nix install Two bugs found running scripts/create-proxmox-resource.sh against a real Proxmox node for the first time: - The Nix installer's single-user root path still shells out to `sudo` to create /nix even though it already detected it's running as root, which fails outright on a minimal, sudo-less Debian/Proxmox node. codex-setup.sh now pre-creates /nix itself so that branch of the installer is skipped. - ensure_remote_repo() only ran scripts/codex-setup.sh right after a fresh git clone, so a bootstrap that cloned the repo but then failed installing Nix (exactly the failure above) left every subsequent run silently building with a `nix` that was never actually installed, since the repo already existing skipped tooling setup entirely. It now checks `command -v nix` (via the same ensure_nix_profile used elsewhere, since a non-interactive ssh session won't otherwise have a single-user install on PATH) on every run and re-bootstraps if it's missing. Both remote build heredocs also now source scripts/lib/nix-bootstrap.sh themselves for the same PATH reason. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-07-20 14:39:43 +00:00

Author

SHA1

Message

Date

beatzaplentyandClaude Sonnet 5

9a1d6842d7

Generalize the remote tooling check to a list of required commands

Check NixOS configurations / eval-hosts (pull_request) Failing after 12m13s

Details

Per-run tooling verification (added in the previous commit) was hardcoded
to checking just `nix`. Turn it into a small array instead, so a future
remote build step needing another tool extends that list rather than
growing a second parallel check.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

2026-07-20 14:42:00 +00:00

beatzaplentyandClaude Sonnet 5

f5ef3194d4

Fix remote-build bootstrap: retry on partial failure, fix sudo-less root Nix install

Two bugs found running scripts/create-proxmox-resource.sh against a real
Proxmox node for the first time:

- The Nix installer's single-user root path still shells out to `sudo`
  to create /nix even though it already detected it's running as root,
  which fails outright on a minimal, sudo-less Debian/Proxmox node.
  codex-setup.sh now pre-creates /nix itself so that branch of the
  installer is skipped.

- ensure_remote_repo() only ran scripts/codex-setup.sh right after a
  fresh git clone, so a bootstrap that cloned the repo but then failed
  installing Nix (exactly the failure above) left every subsequent run
  silently building with a `nix` that was never actually installed,
  since the repo already existing skipped tooling setup entirely. It
  now checks `command -v nix` (via the same ensure_nix_profile used
  elsewhere, since a non-interactive ssh session won't otherwise have a
  single-user install on PATH) on every run and re-bootstraps if it's
  missing. Both remote build heredocs also now source
  scripts/lib/nix-bootstrap.sh themselves for the same PATH reason.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

2026-07-20 14:39:43 +00:00

Fix proxmox remote build bootstrap #16