8000 Need to add host gateway proxy info to NO_PROXY in guest containers · Issue #1293 · abiosoft/colima · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Need to add host gateway proxy info to NO_PROXY in guest containers #1293

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
1 of 5 tasks
rteeling-evernorth opened this issue Mar 26, 2025 · 1 comment
Closed
1 of 5 tasks

Need to add host gateway proxy info to NO_PROXY in guest containers #1293

rteeling-evernorth opened this issue Mar 26, 2025 · 1 comment

Comments

@rteeling-evernorth
Copy link
Contributor

Description

When running Colima when proxy variables set, traffic that is sent to the host gateway( host.lima.internal and its corresponding IP 192.168.5.2) gets routed through the proxy and fails.

It would be convenient to add the host gateway IP and internal dns names to NO_PROXY automatically.

Version

colima version HEAD-7482867
git commit: 74828677e08a79df24a1a1958e5f8e84d7ef4646

runtime: docker
arch: aarch64
client: v28.0.2
server: v27.4.0
limactl version 1.0.6

Operating System

  • macOS Intel <= 13 (Ventura)
  • macOS Intel >= 14 (Sonoma)
  • Apple Silicon <= 13 (Ventura)
  • Apple Silicon >= 14 (Sonoma)
  • Linux

Output of colima status

> colima status
INFO[0000] colima is running using macOS Virtualization.Framework
INFO[0000] arch: aarch64
INFO[0000] runtime: docker
INFO[0000] mountType: virtiofs
INFO[0000] socket: unix:///Users/c43990/.colima/default/docker.sock

Reproduction Steps

  1. run an http server on the guest machine (im using nodejs http-server)
  2. run guest container with curl
  3. curl host.lima.internal or 192.168.5.2

This results in the traffic getting sent to HTTP_PROXY instead of the host gateway. This can be avoided by overriding the NO_PROXY variable with docker run -e "NO_PROXY=${NO_PROXY},host.lima.internal,192.168.5.2"my-container`

Expected behaviour

Colima automatically modifies $NO_PROXY and $no_proxy with host gateway dns names and IP in guest containers for convenience.

Additional context

I would be happy to contribute this, but need some time to determine feasibility and/or find where in the code base the host machine's proxy variables get passed to the guest container.
@rteeling-evernorth
Copy link
Contributor Author

Update:

Colima behaves perfectly fine and the current proxy config code is sufficient. The issue was caused by me leaving cli proxy config in my ~/.docker/config.json that overrode the correct settings configured by colima in the guest machine. After deleting the bad config, the undesired behavior stopped.

Closing issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rteeling-evernorth
< 2A35 /div>
0