In a Docker environment, each container has its own internal file structure. If NZBGet tells Radarr it finished a movie at /downloads/completed , but Radarr’s container doesn’t have a folder named /downloads/completed , Radarr cannot find the file to move it to your library. Common Download Locations in Docker
Usually ${MainDir}/intermediate or /downloads/intermediate How to Fix the "Directory Does Not Exist" Error 1. Standardize Volume Mappings (The Best Fix) In a Docker environment, each container has its
Depending on your specific Docker image (like LinuxServer.io or binhex), the default internal paths usually look like this: /downloads or /data/usenet NZBGet MainDir: Often set to /downloads or /config Standardize Volume Mappings (The Best Fix) Depending on
When you see the error message "," it typically points to a mismatch between how NZBGet reports download paths and how Radarr or Sonarr sees them . This is a common issue in Usenet automation where two isolated Docker containers are trying to share files without the same "vision" of the file system. The Core Problem: Path Mismatch Following the TRaSH Guides recommendation, you should map
Usually ${MainDir}/completed or /downloads/completed
The most reliable way to avoid this error is to use across all your media containers (Radarr, Sonarr, NZBGet). Following the TRaSH Guides recommendation, you should map a single top-level data folder: Host Path: /mnt/user/data Container Path: /data
If you cannot change your volume mappings, you must use within Radarr or Sonarr to "translate" the paths: NZBGet Path and Folder Structure Guide