Docker Compose has Port Conflicts for Port 5000 on macOS Monterey

Unfortunately, the latest version of macOS Monterey uses port 5000 for the internal application Control Center. This causes a port conflict error to be thrown when running the Amundsen Docker instances.

Expected Behavior

Running docker-compose -f docker-amundsen.yml up on macOS Monterey should not product port conflict errors.

Current Behavior

> docker-compose -f docker-amundsen.yml up
Starting neo4j_amundsen ... done
Starting es_amundsen    ... done
Starting amundsensearch   ... done
Starting amundsenmetadata ... done
Recreating 1db7859d4b07_amundsenfrontend ... error

ERROR: for 1db7859d4b07_amundsenfrontend  Cannot start service amundsenfrontend: Ports are not available: listen tcp 0.0.0.0:5000: bind: address already in use

ERROR: for amundsenfrontend  Cannot start service amundsenfrontend: Ports are not available: listen tcp 0.0.0.0:5000: bind: address already in use
ERROR: Encountered errors while bringing up the project.

Possible Solution

We should be able to change services using port 5000 to some other port for local development.

Your Environment

> lsof -i :5000
COMMAND   PID          USER   FD   TYPE  NODE NAME
ControlCe     ...   IPv4   0t0  TCP *:commplex-main (LISTEN)
ControlCe     ...  IPv6    0t0  TCP *:commplex-main (LISTEN)

[cmpadden]

@yoku2010 there is a PR to fix this that was also marked stale.

https://github.com/amundsen-io/amundsen/pull/1814

Since this is impacting so many people, I hope that the change can be made upstream.

[yoku2010]

I was also facing the same issue.

Screenshot of error:

This was apparently due to the new AirPlay functionality. Control Center stops listening to those ports when I turned off “AirPlay Receiver” in the “Sharing” System Preference.

Screenshot of solution:

Now everything is working fine.

I am wondering, why apple choose such a popular port.