FUCKUP #008: The CI Task That Had a Proxy Everywhere Except Where It Needed One
The symptom A task on a CI/automation platform needed to access a public container registry at quay.io. Instead, the task log reported connection refused while it was attempting to reach the registry endpoint at https://quay.io/v2/. The image was public, so registry credentials were not the obvious boundary. The error looked like a remote connectivity failure. What made it weird The surrounding environment already had a working HTTPS proxy configuration. That made the refusal easy to read as evidence against the public endpoint or the network beyond the platform. But the process making the request was not the host or another service with the proxy configured. It was the task itself, running in its own execution context. ...