Codex
0f62fa6d06
The D601 provider-gateway egress proxy (127.0.0.1:18789) is a WebSocket-tunneled CONNECT proxy to backend-core. Long npm downloads (playwright tarball ~3MB, plus tarball streaming) trigger ECONNRESET mid-install, which then compounds into ENOTEMPTY on the next npm retry because the partial global install is not cleaned up. The in-dockerfile retry loop (5 attempts) exhausts and the image build fails at Step 12/37. The build's --build-arg NO_PROXY only listed localhost / 127.0.0.1 / ::1 / host.docker.internal, so every npm fetch went through the proxy. Direct curl tests from D601 to registry.npmjs.org succeed at HTTP 200 with ~280 KB/s, well above what the WS tunnel can sustain for multi-MB downloads. Persist the fix in both D601 and G14 pipeline manifests by adding registry.npmjs.org and .registry.npmjs.org to NO_PROXY so docker build's npm install goes direct. The proxy is still used for apt-get and any other traffic that doesn't match the expanded NO_PROXY list, so unrelated egress continues through the provider-gateway. Refs: #189