avahi daemon - created service not running from inside a container?

Product support
1

I downloaded the avahi daemon tool and can see it running with avahi-daemon --check
I have a service called pix.tcp running (also on windows machines), but on all of our Balena machines, its not running and I can see the other using avahi-browse _pix._tcp -t
This is the service called pix.tcp:

<?xml version="1.0" encoding="UTF-8"?>
<service-group>
  <name>Balena-dev-7_PXLS2_32075_-_Gym</name>
  <service>
    <type>_pix._tcp</type>
    <port>61005</port>
    <txt-record>Description=VPU Description</txt-record>
    <txt-record>GRPCPort=61005</txt-record>
    <txt-record>EventRendererGrpcPort=61007</txt-record>
    <txt-record>Version=3.7.0-dev-17-gcf4efc98d</txt-record>
    <txt-record>VenueID=6355333ba5e7f96cf82bd060</txt-record>
  </service>
</service-group>

Is it not possible to run this from inside a container?