path mapping issue

[audricd]

Hello,

I have the following warning in lidarr while setting up soulseek as a download client:

Remote download client Slskd places downloads in /app/downloads but this directory does not appear to exist. Likely missing or incorrect remote path mapping.

However, neither in local or remote path I am using that path

and yes those are the paths. i dont know if its a bad practice or not, but to avoid headaches, i have them equal, i mount the nas at the same point so its the same all across the containers.

regarding permissions, everything is running as root. yes... bad practice.

lidarr has been set up via the arr script https://wiki.servarr.com/install-script and with root / root
it works well with torrent (qbittorrent on docker). it imports correctly

i have restarted lidarr, removed and re added slskd as a download client, but the exact same error message remains.

[audricd]

i realized the /app/download path came from the path inside the container
moreover, i realized that wasnt mapped anywhere. fixed it:

version: "3.8"

services:
  slskd:
    image: slskd/slskd:latest
    container_name: slskd
    ports:
      - "5030:5030"   # HTTP Web UI
      - "50300:50300" # Soulseek listening port
    environment:
      - SLSKD_REMOTE_CONFIGURATION=true
      - SLSKD_HTTP_PORT=5030
    volumes:
      - /srv/soulseek/data:/app
      - /mnt/nas/musicz:/mnt/nas/musicz
      - /mnt/nas/slskd/downloads:/app/downloads
      - /mnt/nas/slskd/incomplete:/app/incomplete
    restart: unless-stopped

  caddy:
    image: caddy:latest
    container_name: caddy
    ports:
      - "443:443"
      - "80:80"
    volumes:
      - ./caddy/Caddyfile:/etc/caddy/Caddyfile:ro
      - ./caddy/root_ca.crt:/etc/caddy/certs/root_ca.crt:ro
      - caddy_data:/data
      - caddy_config:/config
    depends_on:
      - slskd
    restart: unless-stopped

networks:
  soulseek-net:
    driver: bridge

volumes:
  caddy_data:
  caddy_config:

now i can access the downloads from the container:

however the mapping warning on lidarr remains

[TypNull]

The best place to ask would be the Servarr Discord you’ll get faster responses there since more people are active. Alternatively, you could try the Lidarr Reddit.
Just to clarify: Did you run an install script for Lidarr? If so, that means you’re running Lidarr directly on your system, not in a container, while Soulseek (slskd) is running in a container?

[audricd]

Just to clarify: Did you run an install script for Lidarr? If so, that means you’re running Lidarr directly on your system, not in a container, while Soulseek (slskd) is running in a container?

that is correct. lidarr is set up "bare metal" in an lxc - no docker. whereas, slskd is in another lxc but as a docker container.
does it matter much? arent the paths enough to work together?

[TypNull]

The issue is that slskd downloads files to /app/downloads and reports the same path to Lidarr, but Lidarr can’t find them because the actual location is /mnt/nas/slskd/downloads (or another path, depending on your setup).

You have two ways to fix this:

1. Bind mount the path in your slskd container to match Lidarr’s expected location:
   /mnt/nas/slskd/downloads:/mnt/nas/slskd/downloads
2. Use Lidarr’s remote path mappings to translate the reported path (/app/downloads) to the real path (/mnt/nas/slskd/downloads).
   See: Lidarr Remote Path Mappings

[audricd]

brilliant!! that did it!! thank you very much