Skip to content

fix: add NO_PROXY to test_vm_uses_ipv6_proxy to bypass proxy for registry#218

Closed
claude-claude[bot] wants to merge 1 commit intohttp-proxyfrom
claude/fix-21640434542
Closed

fix: add NO_PROXY to test_vm_uses_ipv6_proxy to bypass proxy for registry#218
claude-claude[bot] wants to merge 1 commit intohttp-proxyfrom
claude/fix-21640434542

Conversation

@claude-claude
Copy link
Copy Markdown
Contributor

@claude-claude claude-claude bot commented Feb 3, 2026

CI Fix

Fixes CI #21640014575

Problem

The test_vm_uses_ipv6_proxy test (and related IPv6/proxy tests) were failing because:

  1. The test sets a fake IPv6 proxy URL: http://[<host-ipv6>]:9999
  2. Podman inside the VM tries to use this proxy to pull alpine:latest
  3. The pull fails with network is unreachable because the VM cannot reach the host's global IPv6 address
  4. slirp4netns IPv6 NAT doesn't make host global IPv6 addresses directly reachable from guests

Error from logs:

dial tcp [fd00::38:d7ff:fefe:c3d1]:9999: connect: network is unreachable

Solution

Added NO_PROXY/no_proxy environment variables to exclude Docker registries (registry-1.docker.io,docker.io) from proxy usage.

This allows:

  • Image pulls to succeed (bypassing the fake proxy)
  • The test to still verify that proxy env vars are correctly passed to VMs (which is the actual intent of the test)

The test's purpose (per its comments) is to verify proxy environment variable propagation, NOT to test actual proxy functionality.

Testing

The fix ensures:

  • alpine:latest pulls succeed without using the proxy
  • Proxy env vars are still set and can be verified in the container environment
  • No changes to actual proxy functionality (other tests cover that)

Generated by Claude | Fix Run

…stry

The test_vm_uses_ipv6_proxy test was failing because it set a fake IPv6 proxy
URL (using the host's global IPv6 address) but this caused podman inside the VM
to try using that proxy for pulling alpine:latest. The pull failed with 'network
is unreachable' because the VM cannot directly reach the host's global IPv6
address - slirp4netns IPv6 NAT doesn't make host global IPs directly accessible.

The test only needs to verify that proxy env vars are passed to the VM, not that
the proxy actually works. The fix sets NO_PROXY/no_proxy to exclude Docker
registries from proxy usage, allowing image pulls to succeed while still testing
that proxy environment variables are correctly propagated.

Fixes CI failure in test_vm_uses_ipv6_proxy and related proxy/IPv6 tests.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
@ejc3
Copy link
Copy Markdown
Owner

ejc3 commented Feb 4, 2026

Superseded by complete test rewrite in PR #217. The old test using fake proxy URLs has been replaced with matrix tests that spin up actual proxy servers and verify requests go through them.

@ejc3 ejc3 closed this Feb 4, 2026
@ejc3 ejc3 deleted the claude/fix-21640434542 branch February 8, 2026 18:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant