rodan5150

First thing, your containers need to have paths mapped like this:
Container path: /data
Host path: /mnt/user/data/*******
 
I'd get rid of any other path mappings for anything media related, obviously keep the appdata path mappings and such. This is for all of the *arrs that would be manipulating files as well as sabnzbd and qbittorrent. This is so that Docker will treat it as one file system, so that atomic moves can happen. If the paths vary at all i.e. your container path on one is "/data" and on another it is "/data/media" this is seen as a separate file system by Docker, and thus no atomic moves.
 
Your Sonarr and Radarr appear to have superfluous mappings to the same stuff, like your /media. There is no need for this. You just pass the "/data" path per above. That would go for Plex as well for that matter (not for atomic moves, but just for simplicity and consistency sake). If I'm setting this up for someone, I typically delete the default mappings to avoid confusion later. All I ever leave is the "/data" or equivalent. Once you have the correct path passed to the container, you just "drill down" to the proper sub directory within the app itself. e.g. in Plex the container needs to have the host mapping "/data/media" so you can internally within Plex, point the TV library to "/data/media/tv" and the movie library to "/data/media/movies" etc. Make sense?
 
Another tip is to use all lower case, being that linux is case sensitive. TV is different from tv, Movies is different from movies, etc. So it is very easy to make a mistakes with path mappings if you mix case Windows style. For example, your radarr is pointed to a host path of "/mnt/user/data/media/Movies" which probably doesn't exist if you made it as "movies" following the trash guide.
 
Straighten all of that out and see if it works. If you have directory permission errors, you can try running the "Docker Safe New Perms" tools under Tools.
 
Hope this helps, and good luck!