ah, standard problem for new docker people - confusing host and container paths
from your volume mappings the sonarr container sees /mnt/downloads
as /downloads
, it also sees /mnt/downloads
as /data
(is that correct? or is it meant to be something else)
sonarr wont see anything under /mnt
as you havent mapped anything from the host into there. its empty because the container image doesnt have anything in there. you mapped in /data
and /tv
so it could use those, but you probably want to use /tv
instead
if you dont care too much about the extra data access the container will have you could remove the mappings for /data
, /downloads
, and /tv
, and just map /mnt
to /mnt
as it appears thats where you want all your downloads and series data anyway? then you can go back to using container paths that look exactly like the host paths (just dont forget they arent - unless you map them)
ie, i presume your download clients will return a path that will be something like /mnt/downloads/...
for any complete job and sonarr wont be able to see it as you dont currently have a /mnt
path.
you could setup a remote path mapping to tell sonarr that /mnt/downloads
is /data
but sometimes its simpler to do it at the volume mapping instead