Running avahi in a separate container

[samalba]

Great work on this image!

Would it make sense to run the avahi daemon in a separate container so you would have to set the option --net=host only on the avahi container to limit the security concern.

At the same time you can then get rid of supervisor and run only netatalk.

[cptactionhank]

Thank you very much :)

I think your suggestion does make sense and it's how I already runs my instance (netatalk+tracker) and the reason for adding the avahi was to make a full get-up-and-running-quick solution. My motivation for making these image is to make it as generic as possible, such that the Hub won't have a billion images for the same service and also work for at least my usage.

I like the idea removing avahi and then supervisor and python as well, which would cause the image to shrink in size. Let's say if there's no significant objections to this then I will go ahead and shave the avahi and supervisor stuff.

[samalba]

Meanwhile I override the default command to "netatalk -d" to not start avahi. So as you mention it's just a matter of image size at this point.

And I still run avahi in a separate container with --net=host.

[steilerDev]

Hi guys,
I would like to achieve the same thing. I also have another docker container running Homebridge, which needs to be advertised over AVAHI as well. Could you please share, how you are achieving the separation of netatalk and Avahi?
Thank you!