Closed janaxhell closed 10 months ago
I just pushed a new version which has better error handling. Please try the new version 1.1.0
(or higher) and update your issue here with any relevant error messages. You can either pull the changes and build/run locally, or simply use the latest public Docker image.
I have the same problem; it looks like there are only ARM64 builds pushed to Docker hub. Running on x86 won't work. https://hub.docker.com/r/krestaino/sptnr/tags
I just pushed a new version which has better error handling. Please try the new version
1.1.0
(or higher) and update your issue here with any relevant error messages. You can either pull the changes and build/run locally, or simply use the latest public Docker image.
I tried the docker-compose again with same exec error, I assume the problem is what basdp said. Anyway I'm not familiar with building from CLI, I always deploy from Portainer, which ins this case seems not pertinent, as this is more a "command" rather than a service. Although would be nice if it was and fired periodically.
@basdp Thank you for pointing that out.
I was able to reproduce this error on my x86 desktop. I have pushed a new version 1.3.0
which now supports linux/amd64
and linux/arm64
. I just tested the new build on my x86 desktop and it's working now. Please pull the latest image and let me know if it's working for you now.
I keep getting exec error. Is it possible that the previous image is not being replaced? How do I clear it without prune command? I have many stopped containers that I don't want to prune, nor start all together. From Portainer I can select the single image I want to remove, but how do I do that from CLI?
@janaxhell You should be able to simply run docker pull krestaino/sptnr:latest
to grab the latest image.
Yes, it's working now. I thought that since krestaino/sptnr:latest
was in the compose, it would pull when I ran the .yml file.
It is showing a lot of albums and songs scrolling now. It will take a long time, I have 33K albums. I'm curious to see how it will look after it's finished.
Wow, that's a ton of albums, good luck! It's going to take days, I would imagine. You might run into rate limiting issues with Spotify too. You may want to consider running the script in batches. See the docs for more info about this and estimated processing times.
https://github.com/krestaino/sptnr?tab=readme-ov-file#resuming-interrupted-sessions https://github.com/krestaino/sptnr?tab=readme-ov-file#estimated-processing-times
I'm going to close this issue now. Feel free to open a new issue if something else comes up.
Hi, I'm trying to deploy the docker-compose.yml, but I'm getting exec error. My compose looks like this
I have added omv1 network because I have not enough non-overlapping IPs. The first time I ran it I got:
I fixed the syntax of omv1 network like above (some apps want it in a way, some others in another) and in this case all I get is:
Also tried to add /music to my Navidrome address AND local IP instead of public domain with same result.
EDIT I'm on Open Media Vault 6 x86.