Description
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
- run an http server on the guest machine (im using nodejs
http-server) - run guest container with curl
- curl
host.lima.internalor192.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.