Docker Desktop host networking conflicts with docker-mac-net-connect and causes login to fail

[lhotari]

Docker Desktop 4.34.0 (release notes) comes with host networking support. This conflicts with docker-mac-net-connect.

The problem digests as docker login failing. In the Docker Desktop UI, there's a popup visible for a few seconds where there's an error message about a port conflict.

Port Conflict
Host Networking: Failed to bind port 61236 on the host. Check if it is already in use

(the port number changes each time)

The problem was resolved by running sudo brew services stop chipmk/tap/docker-mac-net-connect since I had enabled the service when I installed docker-mac-net-connect.

As a resolution to this issue, I guess it would be sufficient to mention this in the documentation of docker-mac-net-connect.

[kmahelona]

Does that mean you don't have to use docker-mac-net-connect to expose the containers' IPs to the host?

[lhotari]

Does that mean you don't have to use docker-mac-net-connect to expose the containers' IPs to the host?

@kmahelona Do I have to use it? If I'd like to be able to access the container IPs, it would continue to be useful. The reported problem here is that docker-mac-net-connect conflicts with Docker Desktop's host network feature and it's hard to find out the reason.