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
I have something that needs to exclusively use port 53 (TCP, ipv4 specifically). If I have it running/bound to 53, and then start colima, I can see that its associated mDNSresponder port picks some random (?) high port. However, if I have the other application off and start colima, it uses 53 by default, and then my other application will fail to start. We had the same issue with Docker Desktop, but successfully used the workaround here: docker/for-mac#7008 (comment)
Does anyone know if there's something equivalent with colima, and/or whether the default port for mDNSresponder can be configured to something other than 53?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I have something that needs to exclusively use port 53 (TCP, ipv4 specifically). If I have it running/bound to 53, and then start colima, I can see that its associated mDNSresponder port picks some random (?) high port. However, if I have the other application off and start colima, it uses 53 by default, and then my other application will fail to start. We had the same issue with Docker Desktop, but successfully used the workaround here: docker/for-mac#7008 (comment)
Does anyone know if there's something equivalent with colima, and/or whether the default port for mDNSresponder can be configured to something other than 53?
Beta Was this translation helpful? Give feedback.
All reactions