-
Notifications
You must be signed in to change notification settings - Fork 9
Can not install Forked DAAPD addon #26
Comments
Hi, That's very strange. Any chance you could grab that forked-daapd.conf file from the container during the build maybe ? I just tried running that command against the default file and I didn't get any errors, but maybe they changed something recently. |
How can I do that? |
Hi, i am facing a similar problem:
|
Same Problem here: System Health
Home Assistant Community Store
Home Assistant Cloud
Home Assistant Supervisor
Lovelace
Spotify
|
Same problem here as well. |
I'm still seeing this issue. Any pointers on where we can look? |
FWIW I get this same error if I just |
Did a bit more digging and this appears to be a result of forked-daapd renaming to owntone |
Hey, yeah there's probably been a lot of changes. Since I don't use this anymore I can't do much about it sorry, if someone wants to take over I'm happy to link to their repo but apart from that I'm just going to archive this I think, sorry. |
@theocoutu your fork looks like the most up to date, I couldn't convince it to work though (expired cert on |
My fork is working for amd64 if anyone's interested (caveat is you have to start the dbus/avahi-damon services in the container manually) |
@ChipWolf |
I think you have to change |
That's fine, and it's not important, just cosmetic ;) It's not my upstream repo at the end of the day and I don't really intend to maintain it (yet) |
@ChipWolf
|
@gieljnssns carefully read the comment |
The text was updated successfully, but these errors were encountered: