Closed mattahorton closed 2 years ago
I'm not sure I can tell you that. You will likely want to search through the original app documentation I have linked to identify. I believe there have been issues opened about ports. Based on the very nature of UPnP and mDNS though, I'm not sure it's a matter of a single port even, it may be ranges of ports at the very least.
Interesting to read that documentation though. I've not been up on my Docker-fu as of late. I wasn't aware that the Win/Mac variants had that restriction as I could swear I had used host networking on my Mac before in testing things. However its quite possible they changed that, or I'm just imaging things! 😜
From the AirConnect README:
In Docker, you must use 'host' mode to enable audio webserver. Note that you can't have a NAT between your devices and the machine where AirConnect runs."
Closing this issue as stale as this is not related to the container.
According to Docker's official documentation --net=host will never work on Docker for Mac or Windows due to platform limitations. This means even adding an AIRCAST_VAR="-b $hostip" will not work because the port is not exposed to Docker.
What are the appropriate ports we need to map using -p to get this to work?