Skip to content

[deep-report] Bind-mount Node.js into AWF chroot so Copilot-engine workflows stop failing with exit 127, 'node' not available #33076

@github-actions

Description

@github-actions

Context

Multiple Copilot-engine workflows are failing immediately at entrypoint:

[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.

This is a sandbox-bootstrap regression, not user error. The entrypoint already hints at the fix: "verify the install path is present and bind-mounted into /host".

Affected workflows (24h–48h sample)

Why it matters

Five workflows fail every scheduled run for free — this is the dominant signature in today's [aw] failed issue cohort. Open [aw] *failed count climbed from 9 → 11 in 24h, with most of the new additions coming from this single root cause.

Proposed fix

In the AWF chroot setup step (likely in the activation job template), bind-mount /opt/hostedtoolcache/node (the runner-cached Node from actions/setup-node) into the chroot, or chain setup-node before AWF chroot activation. Once node is on PATH inside the chroot, the Copilot CLI entrypoint succeeds.

Suggested agent

A workflow-infrastructure-aware agent (e.g. PR Sous Chef on a chroot-related branch) — needs to touch the activation job template, not the workflow markdowns.

Estimated effort

Small: a single change to the chroot bootstrap script + verifying one of the failing workflows now runs to completion.

Source

DeepReport Intelligence Briefing 2026-05-18; Weekly Workflow Analysis #33009; Daily Audit #32908.

Generated by 🔬 DeepReport - Intelligence Gathering Agent · ● 19.5M ·

  • expires on May 20, 2026, 4:10 PM UTC

Metadata

Metadata

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions