i’m trying to setup Music-Assistant as App (Docker) in Truenas 26.0.0-BETA.1. Has anyone successfully integrated players using AirPlay and DLNA? For me i just get Chromecast and Sonos working. So far i’ve setup Host Network and disabled mDNS in the Truenas Network Configuration - but no luck. When using Music-Assistant on ‘pure’ Debian with Docker everything works as expected and i do get all my players registered (so Network etc. can be ruled out)
Found the issue - seems newer versions of music-assistant do have only one player entry (and there the output protocol can be selected) vs. older versions do have separate entries per player per protocol …
Would you be able to elaborate a bit please?
I was never able to configure Music Assistant correctly. It can’t discover any players aside the one that is in the browser.
What I have tried so far
- If I leave MA on host networking - it won’t start at all. Similar to what this post points to Music Assistant Server mDNS conflict
- However - the above post is in Docker and I am running the default app. Still - there is a conflict
-
[31m2026-07-06 15:23:21.069 ERROR (MainThread) [zeroconf] Address in use when binding to ('', 5353); When using avahi, make sure disallow-other-stacks is set to no in avahi-daemon.confe[0m - I did consider disabling mDNS on the networking section but I am also using Time Machine so this is not an option.
If you can point me in the right direction - I would appreciate it.
Perhaps don’t use host networking for this app? Why is it needed? The reason for preventing multiple mDNS stacks from running concurrently on host is to avoid UB in critical NAS functions.