-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
/etc/snapserver.conf not found on armhf #9
Comments
Same problem here |
Glad to hear I wasn't the only one experiencing this. It seems like it's something that's only a problem in the latest release. If I pull the |
Yes, I tried to workaround the current problems with building for armv7 and messed the latest build up on this occasion.. Please use |
I'm on a rPi 4 running latest version of RaspOS and tried to pull the old 19.0 image for arm devices. When i try to run it snapserver starts ok but librespot fails to start "version GLIBC_2.28 not found (required by /home/localuser/librespot)" Looks like version 2.27 is running in the container but 2.28 is installed on my host. Any way around this? |
@bbgehring Not sure what you are doing there. The image contains both snapserver as well as librespot so you don't need a librespot installation on your host. Just start the container and snapserver will take care of starting librespot as well. |
@djmaze sorry that wasn't the exact error output I was typing from memory. Librespot isn't installed on host. Pulled the previous version of your image for arm and when docker running this is the log I'm receiving from within the container. I just checked to verify the version of GLIBC in the container and it's 2.27.
|
Okay, so that's the armv7 version. I just try it out myself. You are right, that version seems broken unfortunately. For now, you could go back one more version and use the |
Also happens on x86 |
Please try the latest image, it should now work on all architectures. |
Hi,
When I try to create a container with your image I get an error:
Is the image broken?
The text was updated successfully, but these errors were encountered: