Repository navigation
Conversation
Expose the physical coreutils applet directory to Cloud Hypervisor AWF processes while preserving PATH precedence and host-tool trust checks. Cover primary agents and enclaves without changing other runtimes. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Ubuntu 26.04 exposes the system
idcommand through a symlink, which AWF v0.29.0 rejects during its trusted host-tool preflight. This prevented the agent from starting in Daily AWF Spec Compiler Surfacing Review run 40593497628.Append
/usr/lib/cargo/bin/coreutilsto the privileged Cloud Hypervisor AWF process's PATH so it can resolve the physicalidapplet. This follows the physical applet handling in the upstream AWF fix, which is not yet in the published v0.29.0 release.Validation
make agent-report-progresspassed build, formatting, Go/custom lint, impacted tests, schema freshness, and workflow drift checks.No workflow was dispatched or rerun, so hosted Ubuntu 26.04 recovery remains unverified. Optional Docker-based scanners were not run because the local Docker daemon was unavailable.