Exit Code 126 in CI: What It Means and How to Fix It
Exit code 126 means the command exists but could not be executed - usually a permissions or interpreter problem.
The shell found the command but could not run it.
What it means
Found-but-not-executable: missing execute permission, wrong architecture, or a broken shebang.
Common causes
- The script lacks
+xpermission. - A broken or missing interpreter on the shebang line.
- Wrong-architecture binary.
How to fix it
Run chmod +x script, verify the shebang points to an installed interpreter, and confirm the binary matches the runner architecture.
Related guides
Docker "permission denied while trying to connect to the Docker daemon socket"Fix "permission denied while trying to connect to the Docker daemon socket" in CI - caused by the user not be…
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…