Exit Code 127 in CI: What It Means and How to Fix It
Exit code 127 means the shell could not find the command - a missing tool or a PATH problem.
The shell searched PATH and found nothing matching the command name.
What it means
Command not found: the binary is not installed or not on PATH.
Common causes
- The tool is not installed on the runner.
- PATH does not include the install location.
- A typo in the command name.
How to fix it
Install the tool (or add a setup step), and ensure its directory is on PATH. On self-healing runners, a missing known package can be installed and the step retried automatically.
Related guides
Self-Healing CI: Missing System Packages and Setup GapsA missing system library or tool fails the build until someone installs it. See the manual fix and how self-h…
Exit Codes and Signals in CI/CD: A Practical GuideA practical guide to process exit codes and signals in CI/CD - what 1, 2, 124, 126, 127, 130, 137, and 143 me…
CI Exit Code Lookup: What Does This Exit Code Mean?Instant lookup for CI/CD process exit codes - enter a code (137, 127, 143…) to see what it means, whether it…