Problem Statement

The Daily News workflow failed at engine startup with exit code 127 because the Copilot CLI could not find node inside the AWF chroot environment. The agent never started — this is a complete pre-activation failure.

Affected Workflows and Runs

• Workflow: Daily News (Copilot CLI engine)
• Failed run: §25311165057 — 2026-05-04T09:20Z
• Engine version: GitHub Copilot CLI v1.0.40, model claude-sonnet-4.6
• Other Copilot CLI workflows may be equally affected if the runner configuration is shared

Root Cause

The AWF chroot environment did not have node on its PATH. The Copilot CLI requires Node.js at runtime. The runner's Node.js install (via setup-node, nvm, or /opt/hostedtoolcache) was either not present or its bin/ directory was not bind-mounted into the chroot.

Error log:

[entrypoint][ERROR] Copilot CLI requires Node.js, but 'node' is not available inside AWF chroot.
[entrypoint][ERROR] Ensure Node.js is installed on the runner and reachable from PATH inside the chroot.
[entrypoint][ERROR] Example locations include /opt/hostedtoolcache/... and /home/runner/.nvm/...
[WARN] Command completed with exit code: 127
Process exiting with code: 127

Probable Root Cause

One of:

1. setup-node step ran but its toolcache path is not bind-mounted into the chroot
2. Runner image changed and no longer ships Node.js at the expected location
3. Workflow/runner misconfiguration where PATH inside chroot differs from host PATH

Proposed Remediation

1. Check the runner's /opt/hostedtoolcache and ~/.nvm for the Node.js binary location
2. Verify the AWF chroot bind-mount configuration includes the Node.js bin/ directory (or set GH_AW_NODE_BIN env var to the absolute path)
3. Add a pre-flight check in the Daily News workflow: node --version || echo 'Node.js missing' before the agent step
4. Check if other Copilot CLI workflows on the same runner are also failing

Success Criteria

• Daily News completes next scheduled run without exit code 127
• Copilot CLI engine runs are stable across other workflows on the same runner

Parent Issue

Part of failure investigation report: #aw_fail6h (2026-05-04 6h window)

Generated by [aw] Failure Investigator (6h) · ● 239K · ◷

• expires on May 11, 2026, 1:23 PM UTC