shairport-sync-docker icon indicating copy to clipboard operation
shairport-sync-docker copied to clipboard

Missing user information when running in Unraid

Open timbrueggenthies opened this issue 3 years ago • 5 comments

I'm trying to run the shairport-sync-docker container in unraid. As I am only using a pipe to forward the audio to, the only two things added are:

-v /tmp/snapcast:/tmp/snapcast -> The location of the pipe
-v /mnt/domains/shairport:/etc -> The location of the shairport config file

However, when starting the container, following errors appear.

dbus[8]: Could not get password database information for UID of current process: User "???" unknown or no memory to allocate password entry

dbus[8]: Unknown username "root" in message bus configuration file
dbus[8]: Could not get password database information for UID of current process: User "???" unknown or no memory to allocate password entry

dbus[8]: Unknown username "root" in message bus configuration file
dbus[8]: Could not get password database information for UID of current process: User "???" unknown or no memory to allocate password entry

dbus[8]: Unknown username "root" in message bus configuration file
dbus-daemon[8]: Could not get password database information for UID of current process: User "???" unknown or no memory to allocate password entry

dbus-daemon[8]: Failed to start message bus: Could not get UID and GID for username "messagebus"

Do you have an idea what is going wrong there? Thanks in advance.

timbrueggenthies avatar Apr 18 '21 05:04 timbrueggenthies

Thanks for the post. It's some kind of D-Bus issue. D-Bus is used by Avahi and also, optionally, by Shairport Sync itself.

mikebrady avatar Apr 26 '21 12:04 mikebrady

Hi there. just wondering if you made any progress with this. I'm not familiar with Unraid, I'm afraid.

mikebrady avatar Aug 15 '21 09:08 mikebrady

TBH i got carried away by the topic, as I don't have that much time lately for this stuff. I will try again in the coming week, Unraid also received a relatively big update a few month back. Maybe this has solved the issue.

timbrueggenthies avatar Aug 21 '21 12:08 timbrueggenthies

The error remains, but I also don't have the time to look further into it.

timbrueggenthies avatar Sep 10 '21 12:09 timbrueggenthies

No worries -- thanks for the update.

mikebrady avatar Sep 10 '21 13:09 mikebrady