[awf] cli-proxy: awf-cli-proxy container exits(1), blocking Contribution Check workflow

[lpcox]

Problem

The awf-cli-proxy sidecar container exits with code 1 on startup, causing the copilot engine to fail with: dependency failed to start: container awf-cli-proxy exited (1).

Context

• Original issue: [aw] Contribution Check failed gh-aw#38118
• Failed run: https://github.com/github/gh-aw/actions/runs/27210418799
• Workflow: Contribution Check
• Affects all workflows using the copilot engine that depend on awf-cli-proxy

Root Cause

The awf-cli-proxy container is failing at startup (exit code 1) before the agent container can start. Since the agent depends_on the cli-proxy being healthy, the entire workflow aborts. This appears to be a recent regression (multiple workflows failing with identical errors on June 9–10, 2026), suggesting a broken container image or misconfigured entrypoint in the cli-proxy component.

Proposed Solution

1. Inspect awf-cli-proxy container logs for the specific startup error (e.g., missing env vars, port conflicts, or image pull failure).
2. Check for recent changes to containers/cli-proxy/ that may have introduced the regression.
3. Verify the cli-proxy image tag/digest is consistent with the deployed AWF version.
4. Add a healthcheck or startup probe to emit a clearer error on failure.

Generated by Firewall Issue Dispatcher · 147 AIC · ⊞ 27.8K · ◷

[github-actions]

👋 Hello! I noticed this issue might be related to existing open issues describing the same root cause:

• [awf] cli-proxy: awf-cli-proxy container exits(1), blocking UK AI Operational Resilience workflow #4607 — awf-cli-proxy exits(1), blocking UK AI Operational Resilience workflow
• [awf] cli-proxy: awf-cli-proxy container exits(1), blocking Breaking Change Checker workflow #4609 — awf-cli-proxy exits(1), blocking Breaking Change Checker workflow
• [awf] cli-proxy: awf-cli-proxy container exits(1), blocking AIC Usage Optimizer workflow #4610 — awf-cli-proxy exits(1), blocking AIC Usage Optimizer workflow

All four issues describe the identical problem: awf-cli-proxy container failing at startup (exit code 1), preventing dependent agent containers from starting. This appears to be a widespread regression affecting all workflows using the copilot engine with awf-cli-proxy.

You may want to consolidate these into a single tracking issue. If one of the above already covers your report, consider closing this as a duplicate.

This is an automated message from the issue duplication detector.

Generated by Issue Duplication Detector for issue #4608 · 81 AIC · ⊞ 32.9K · ◷