Can't bind to private address on host

[michalno1]

Description

After moving from Docker for Mac to Colima I noticed that I can no longer publish to a private address on the host. For example, assuming the private address of my mac is 192.168.1.17, this works on Docker for Mac:

docker run --privileged --tty --publish=192.168.1.17:59424:6443/TCP kindest/node:v1.23.4

but it doesn't work on colima:

docker: Error response from daemon: driver failed programming external connectivity on endpoint heuristic_leakey (b3989fd86d3b82abed9e160d7e2292a41a4f9f65a80500e8d82a8ee5ca1a2b70): Error starting userland proxy: listen tcp4 192.168.1.17:59424: bind: cannot assign requested address.

Version

Colima Version: 0.4.6
Lima Version: 0.13.0
Qemu Version: 7.1.0

Operating System

• macOS Intel
• macOS M1
• Linux

Expected behaviour

I would expect to be able to bind to private address on the host.

[abiosoft]

The network behaviour is a bit different to Docker Desktop but it can be made to work. If at all this is done, it will only support the network interface for the default route.

What is the main use case for this? Limiting access to devices on the LAN?

[inabhi9]

@abiosoft what do you mean by support the network interface for the default route?
I'm also interested in the feature and yes, use case is limiting access on LAN.

For now, I patched the latest source to accept port interface (which was available somewhere in v0.3) and pass it to port forwards.

However, I'm curious if it can be done similar to Docker like ability to pass down host interfaces to VM.

[abiosoft]

This feature is now implemented and would be part of the next release.

To try it now:

# remove stable version
brew uninstall colima

# install development version
brew install --head colima