Closed CaseyRo closed 3 years ago
I can reproduce this on a raspberry pi 4. It seems forked-daapd crashes when it tries to initialize a Spotify session
. The architecture of libspotify.so
appears to be correct. I was not able to retrieve much more information. It might be an incompatibility between the glibc
it was built against and the musl libc
it is actually getting from Alpine.
I currently have no useful workaround suggestions. Perhaps it works by rewriting the Dockerfile to use baseimage-ubuntu:arm32v7-focal
.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
I am hijacking this one because I also can't get Spotify to work in the latest version. There is not even a "Spotify" integration in the logs for me.
> cat /sys/firmware/devicetree/base/model
Raspberry Pi 3 Model B Rev 1.2
> uname -srm
Linux 5.4.51-v7+ armv7l
> docker inspect ghcr.io/linuxserver/daapd | grep -iE ".*(architecture|variant|version).*"
"linuxserver/daapd:version-27.2",
"build_version": "Linuxserver.io version:- 27.2-ls32 Build-date:- 2020-12-16T17:33:40+00:00",
"DockerVersion": "19.03.13",
"build_version": "Linuxserver.io version:- 27.2-ls32 Build-date:- 2020-12-16T17:33:40+00:00",
"Architecture": "arm",
> docker logs daapd
[ LOG] main: Forked Media Server Version 27.2 taking off
[ LOG] main: Built with:
[ LOG] main: - ffmpeg
[ LOG] main: - iTunes XML
[ LOG] main: - LastFM
[ LOG] main: - Chromecast
[ LOG] main: - MPD
[ LOG] main: - Device verification
[ LOG] main: - Websockets
[ LOG] main: - ALSA
[ LOG] main: - Webinterface
[ LOG] main: mDNS init
[ LOG] mdns: Avahi state change: Client running
I have seen that the arm64 image seems to be broken but I don't use it. What I am doing wrong?
EDIT: OK. still broken... you should definitely update the "Versions" section in the Readme to not confuse people :-)
Currently, I do not see a way to fix libspotify for ARM in Alpine Linux. To get a more 'durable' solution, I extended this container with librespot in #44 .
As a temporary workaround, you can build https://github.com/bverhagen/docker-daapd-librespot yourself.
Has there been any progress on this? I would love to be able to use forked-daapd but I do need Spotify as all my music is there....
fyi I am currently working on a version of forked-daapd (now called owntone) that doesn't require libspotify. Instead, Spotify support is built in.
This repo already builds from the owntone repo, so I guess spotify should work on arm32 then? @ejurgensen
I wouldn't think so, this change is in an unmerged development branch. It needs more testing and fixing up before going into master - as you can see it is also a draft PR.
Sorry, I misread what you wrote and didn't get that it was a different branch. Would we have to do anything before it's merged or is it good to go when it's merged?
I am not sure exactly how the Docker image is built, so can't say. I also haven't decided yet whether it should be enabled by default or if it will require a --enable-spotify
configure flag.
We build it from source, so then we'll have to enable it if it's not enabled by default. And add dependencies, if needed.
@snizzleorg : Did you consider the docker-daapd-librespot solution? It is not perfect (the pipe interface is sensitive to the order in which you start/stop things), but does get you started with forked-daapd + Spotify. As mentioned above, forked-daapd + libspotify works on Debian-based distro's. You can install them natively or build the Docker image yourself.
@bverhagen thanks for the suggestion. I have librespot running on a raspberry Pi. and it works ok with forked-daapd. BUT my use case is different I want to actually use forked-daapd to play the library. That works much more reliable... I actually have all I want working on a rapsberry-pi but I want to move it onto my home-assistant installation and use docker for that. basically to get rid of one too many devices...
@ejurgensen : Thank you for the work on the new Spotify client. I am currently tracking owntone/owntone-server#1230 (only for ARM64) here: https://github.com/bverhagen/docker-daapd/tree/spotify1c. I am currently testing this on my aarch64 setup.
You are invited to build the Docker yourself - although keep in mind it is still a feature in development.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Expected Behavior
Using spotify should work in ARM 32 bit version
Current Behavior
"online services" menu shows:
forked-daapd was either built without support for Spotify or libspotify is not installed.
Steps to Reproduce
dockerfile.armhf
missed the 'enable-spotify' flag, so added thatLIBSPOTIFY_CFLAGS
andLIBSPOTIFY_LIBS
to the dockerfileEnvironment
OS: Debian Buster CPU architecture: arm32 How docker service was installed: Using raspi to run docker, build as stated above.
Command used to create docker container (run/create/compose/screenshot)
Used docker compose to start (pastebin link)