Balena Supervisor & Avahi

Product support
4

Hi Cameron,

thanks for the response. I have a multi container project running on a balena fin 1.0 where several of the containers should expose services over MDNS / Avahi. So far:

  1. The host id.local is advertised by host os
  2. The zoo publisher example also advertises its services. However it using SystemD and creates an avahi service file.
  3. I have a node js application that uses the mdns npm module but it exposes programmatically its services and has no systemd.

What seems to happen is that I can see all service definitions in the subnet (using Discovery on a Mac) but the ones from the container on item 3 above have 0 items.

Do I have to mimic the zoo example or can I somehow programmatically tell the avahi daemon about these services?

Thanks in advance,

Alex Kritikos