Troubleshooting #

SymptomFix
Anything unclear about the machinenomarmy doctor, then nomarmy health
A worker's commands come back Aborted, even simple reads, or jobs fail in ways that make no sense (macOS, Windows)macOS: the Podman VM is too small: every sandbox, verification run and image build shares its memory, and Podman's default is 2 GiB. nomarmy sandbox shows it; nomarmy sandbox --memory 8 resizes it (doctor fails below 4 GiB). Windows: Podman runs inside WSL and shares WSL2's memory (about half the machine by default); raise memory= under [wsl2] in %UserProfile%\.wslconfig, then wsl --shutdown
Every sandbox fails to start with error during chown ... permission denied or insufficient UIDs or GIDs available in user namespace, often right after the Podman VM restartedRootless Podman lost its subordinate ID ranges (/etc/subuid, /etc/subgid emptied). nomarmy doctor detects it; nomarmy sandbox --repair restores them (it waits until no job is running, since it restarts Podman's containers)
The disk fills up with old imagesnomarmy sandbox --prune removes images no container uses; nomArmy rebuilds its own when a job needs them
No API key found for provider "llama-cpp" during e2e.sh./scripts/configure-openclaw.sh <profile>, then rerun
A job fails with, or is refused for, model_not_foundYour plan or OpenClaw can't run that model (nomArmy tests an unproven model before its first job). nomarmy agents list shows which roles use it; nomarmy army assign <role> <agent> <model> moves the role and tests the new model
Verification fails on a missing packageNode: commit each package's package-lock.json (yarn, pnpm and workspaces aren't installed yet). Python: list your requirements files under environment.python.requirements
A config change didn't take effectnomarmy stop && nomarmy start for inference; restart your coordinator after nomarmy connect or an update
git worktree add fails with Filename too long (Git for Windows)git config --global core.longpaths true. Job worktrees on Windows are made by Git inside WSL, which has no such limit
Not sure a setting fits your hardwarenomarmy sizing, or nomarmy sizing --check