Colima equivalent of Docker's "Enable host networking"

[ethanjdiamond]

Description

In local development, I'm running several services locally on my machine. Some are running in a docker container, and some are running directly on my host machine. This has been working fine when I use the Docker app and stock Docker daemon as long as I have "Enable host networking" turned on.

I've been wanting to switch to Colima since the memory use and perf is better, but it looks like using the --network-address setting only appears to expose the ports from inside Colima to localhost on my host machine without exposing the ports running on my local machine to localhost inside of Colima. Would it be possible to allow the port sharing to be birectional?

[abiosoft]

Can you clarify what you mean by bidirectional. You want services running on your machine to reach services running in the container?

[jtbaker]

Can you clarify what you mean by bidirectional. You want services running on your machine to reach services running in the container?

@abiosoft my goal is to do the same thing. I want to run ollama on the host (a mac mini - macos doesn't expose APIs for the GPU to containers) and I want to run containers in a cluster on the VM that point to the port on the host where ollama is exposed.

[abiosoft]

@jtbaker in that case, you cannot access ports on the host via localhost in the containers. You would need to either specify the host which should be reachable via host.docker.internal or the fixed IP 192.168.5.2.

[Crown0815]

Is this related to #1174?