Network address does not populate when connected to VPN

[Spirarel]

Description

Preamble

Very sorry if this is a duplicate, I've seen many similar issues on GH and around the web, but none quite like this. Seems like it could be user error, I just didn't have this issue before a macOS update. Thanks for maintaining this otherwise great software!

Issue

While connected to my corporate VPN I'm unable to connect to docker containers exposed on localhost with a forwarded port.

Notably running colima ls displays no network address when the container is spun up on VPN, but does display on VPN. In order to get an accessible container, I have to tediously log out of the VPN, spin it up, then log back in.

Attempted fixes

• Asking coworker (he gave up and installed podman)
• Setting network address in colima config to true
• Setting network address to false and host addresses to true
• Uninstalling and reinstalling.

Version

colima version 0.8.1
git commit: 96598cc

runtime: docker
arch: aarch64
client: v28.0.0
server: v27.4.0
limactl version 1.0.6
zsh: command not found: qemu-img

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: sshfs
INFO[0000] socket: unix:///Users/trpkq59/.colima/default/docker.sock

Reproduction Steps

1. Sign on to my corporate VPN (sorry...)
2. docker run a container with an exposed port
3. Attempt to connect

Expected behaviour

Connection would be uneventful

Additional context

This problem may have been introduced with the Sequoia update, but I'm not positive on that.

[MatthewRyanRead]

I have the same issue on an Apple M1 with Sequoia 15.4.1, identical Colima version as you, qemu-img version 9.2.3. The VPN client is Cisco Secure Client 5.1.9.113, in case that matters.

If I connect the VPN after starting Colima, nothing changes in the output of colima status nor colima ssh -- ip route:

$ colima status
INFO[0016] colima is running using macOS Virtualization.Framework 
INFO[0016] arch: aarch64                                
INFO[0016] runtime: docker                              
INFO[0016] mountType: virtiofs                          
INFO[0016] address: 192.168.106.2                       
INFO[0016] socket: unix:///Users/mread/.colima/default/docker.sock 

$ colima ssh -- ip route
default via 192.168.5.2 dev eth0 proto dhcp src 192.168.5.1 metric 200 
default via 192.168.106.1 dev col0 proto dhcp src 192.168.106.2 metric 300 
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
192.168.5.0/24 dev eth0 proto kernel scope link src 192.168.5.1 metric 200 
192.168.5.2 dev eth0 proto dhcp scope link src 192.168.5.1 metric 200 
192.168.106.0/24 dev col0 proto kernel scope link src 192.168.106.2 metric 300 
192.168.106.1 dev col0 proto dhcp scope link src 192.168.106.2 metric 300 

But when I connect the VPN first:

$ 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/mread/.colima/default/docker.sock 

$ colima ssh -- ip route
default via 192.168.5.2 dev eth0 proto dhcp src 192.168.5.1 metric 200 
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
192.168.5.0/24 dev eth0 proto kernel scope link src 192.168.5.1 metric 200 
192.168.5.2 dev eth0 proto dhcp scope link src 192.168.5.1 metric 200 

In both cases, I cannot connect to my local containers using 192.168.106.2 when connected to the VPN. I can connect after disabling the VPN without restarting Colima, or if I use localhost.

Using the --dns flag has no impact (I tried 1.1.1.1 and 8.8.8.8), nor does deleting either of the default routes.