I've made a Docker container which runs a
forked-daapd (a DAAP server publishing over mDNS with a single port 3689 for HTTP requests) and exposes the port properly to the host operating system:
sudo docker run -it --rm -v /home/naftuli/Music:/srv/music -p 3689:3689 \ daapd /sbin/my_init
The problem is that this service never gets published properly to mDNS because its IP address (some internal Docker IP range) doesn't really work. I could run it with
--net=host, but that's potentially pretty dangerous as I'm basically handing my network adapter to the container.
Is there a way for me to publish this service and have mapping work as planned?