You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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?
The text was updated successfully, but these errors were encountered: