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
Using 5000 creates conflicts system-level conflicts for MacOS Airplay Receiver, Intel Graphics Command Center, and developer conflicts for Node.js, Heroku, ASP.NET Core, Docker Registry, etc.
This invariably creates a number of headaches for anyone trying to use the "quick start" Docker Deployment guide.
The text was updated successfully, but these errors were encountered:
Hello! I’d like to work on this issue regarding the port conflict with port 5000 in the Docker deployment. I propose to modify the Docker configuration to use a different default port (such as 5001 or 8080) and update the documentation to guide users who may still need port 5000. I believe this will help reduce conflicts with MacOS AirPlay Receiver, Intel Graphics Command Center, and other developer tools that use port 5000.
Please let me know if there are any specific guidelines or if I should proceed with these changes.
Thank you!
The IANA has long considered port 5000 (along with 1900) for network device discovery.
Using 5000 creates conflicts system-level conflicts for MacOS Airplay Receiver, Intel Graphics Command Center, and developer conflicts for Node.js, Heroku, ASP.NET Core, Docker Registry, etc.
This invariably creates a number of headaches for anyone trying to use the "quick start" Docker Deployment guide.
The text was updated successfully, but these errors were encountered: