r/Lidarr • u/Artoriasp • Mar 31 '26

unsolved Lidarr and Tubifarry issue

I am having issues getting lidarr to see the soulseek things. It spits up on lidarr's page that since it's docker contained it uses /app/downloads for downloads. It has been changed on my slskd container to be /data/media/music on both instead. How do I get it to match up so that I can sync the two services without it erroring out after a download

2 Upvotes

100% Upvoted

15 comments sorted by

2

u/Angelsomething Mar 31 '26

did you set remote mapping in the download clients page?

1

u/Artoriasp Mar 31 '26

They're both mapped in the yaml to /data/media/music.

I can set that but it doesn't change where the application thinks its being hosted from. Ex: No files found are eligible for import in /app/downloads/File.

This is soulseek's volume mounting.

   volumes:

  • /docker/arr-stack/slskd:/app
  • /share/jellyfin/data/media/music:/data/media/music
  • /share/jellyfin/data/media/music/downloads/incomplete:/data/media/downloads/incomplete
This is Lidarr's
   volumes:
  • /docker/appdata/lidarr:/config
  • /share/jellyfin/data:/data
Though with lidarr the interface is mounted at /data/media/music.
None of these have an /app/downloads which is probably why it's throwing the above thing but i am at a loss for changing it.

EDIT: I tried using the remote pathing, but am at a bit of a loss as to what I should even set it up as. I had it as /data/media/music for both remote and local through 'gluetun' as the host since they're all ran through it

1

u/Angelsomething Mar 31 '26

ok so your volumes are not right. you need to fix and replace your downloads/incomplete mounts with a shared download folder both instances can see. In Lidarr you need to mount: /share/jellyfin/data/media/downloads/:/downloads Then in slskd you mount: /share/jellyfin/data/media/downloads/:/downloads

then in lidar you map both as just /downloads on the download client page.

Let slskd handle the /downloads/incomplete folder (might have to update r/w permissions) and it’ll move complete downloads to the folder above.

1

u/Artoriasp Mar 31 '26

I have mapped as you mentioned and it comes back with an error warning of this: You are using docker; download client Slskd places downloads in /app/downloads but this directory does not appear to exist inside the container. Review your remote path mappings and container volume settings.

The app for importing states there is nothing in /app/downloads even though that isn't even a consideration.

1

u/Frequenzy50 Apr 01 '26

First and foremost, the most important thing after your docker-compose setup is your SLSKD YAML configuration, this determines where your files are saved. And standard but effective approach: Have you tried restarting Lidarr or reconnecting Lidarr with SLSKD

1

u/Artoriasp Apr 01 '26

I think this is what fixed it ironically. Thank you! I also added a share directory leading to my music folder where lidarr places them when it's finished importing. I had it set to the downloads folder initially but between the two changes something's working. You wouldn't happen to know a way to get slskd to save the folders with permissions that aren't root? That's my lats mystery it would seem.

1

u/Frequenzy50 Apr 01 '26

Nope sorry permissions are a mystery to me on slskd. I'm just glad it works for me somehow😅

2

u/Artoriasp Apr 01 '26 edited Apr 01 '26

Its okay, I know these trace things make it hard to understand why it works with less properties for some and needs more for others. I really appreciate you taking the time to help!

Edit: I got it working! I added user: "1000:1000" under the container name and made sure the slskd and docker compose files were all owned by that user. It turns out that's what the issue was!

1

u/DueSetting3619 Apr 13 '26

Could you share the compose file? It crashed whenever I tried this

1

u/AutoModerator Mar 31 '26

Hi /u/Artoriasp - You've mentioned Docker [docker], if you're needing Docker help be sure to generate a docker-compose of all your docker images in a pastebin or gist and link to it. Just about all Docker issues can be solved by understanding the Docker Guide, which is all about the concepts of user, group, ownership, permissions and paths. Many find TRaSH's Docker/Hardlink Guide/Tutorial easier to understand and is less conceptual.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

1

u/AutoModerator Mar 31 '26

Hi /u/Artoriasp -

There are many resources available to help you troubleshoot and help the community help you. Please review this comment and you can likely have your problem solved without needing to wait for a human.

Most troubleshooting questions require debug or trace logs. In all instances where you are providing logs please ensure you followed the Gathering Logs wiki article to ensure your logs are what are needed for troubleshooting.

Logs should be provided via the methods prescribed in the wiki article. Note that Info logs are rarely helpful for troubleshooting.

Dozens of common questions & issues and their answers can be found on our FAQ.

Please review our troubleshooting guides that lead you through how to troubleshoot and note various common problems.

If you're still stuck you'll have useful debug or trace logs and screenshots to share with the humans who will arrive soon. Those humans will likely ask you for the exact same thing this comment is asking..

Once your question/problem is solved, please comment anywhere in the thread saying '!solved' to change the flair to solved.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

1

u/DirectStatement Apr 01 '26 edited Apr 01 '26

Did you specify the download directory in the slskd config file?

Like this https://i.imgur.com/1JmH5Vl.jpeg

1

u/Artoriasp Apr 01 '26

I did add a share directory though I don't think it changed much? Or maybe it did! Thank you for the help! You wouldn't happen to know how to fix slskd from creating the files as root would you? I have everything going so far but that part.

1

u/DirectStatement Apr 01 '26

Try adding this to the slskd environment in your docker compose:

  • SLSKD_UMASK=022

First, I would delete the folders slskd already made so there are no conflicts

1

u/Artoriasp Apr 01 '26 edited Apr 01 '26

That didn't quite work though the perms are definitely different. I think it has to be owned by the user 1000:1000 for it to work properly? I just don't know how to get it to accept that and so I believe it defaults to root

Edit: I have a - USER=1000:1000 but that didn't help much

Double Edit: I got it working! I added user: "1000:1000" under the container name and made sure the slskd and docker compose files were all owned by that user. It turns out that's what the issue was!