didericis
f9078bb6c6
tracker-policy-pr / check-pr (pull_request) Successful in 10s
test / integration-docker (pull_request) Successful in 16s
lint / lint (push) Successful in 49s
test / unit (pull_request) Successful in 1m40s
test / integration-firecracker (pull_request) Failing after 2m50s
test / coverage (pull_request) Has been skipped
test / publish-infra (pull_request) Has been skipped
This is the layer that actually decides it, and it was in the script from the start: ~/.docker/config.json's proxies block is what the Docker CLI copies into every container it starts. Being client-side it beats the podman service outright, which is why containers.conf `env`, http_proxy=false, and the service environment each looked correct on disk and changed nothing a nested container saw. Also corrects the comment on the service-env substitution, which claimed to be the one place the address sticks. It is not; it covers podman's own pulls and non-CLI API clients. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>