• 7 Posts
  • 11 Comments
Joined 2 months ago
cake
Cake day: July 3rd, 2024

help-circle


  • Thanks for your insights.

    The router is set up to give the PC a static IP already. I have now gone into the Networks page in Ubuntu desktop, set the IPv4 method from Automatic DHCP to Manual, and added my static IP there.

    The arrs and other docker containers all use the same bridge network (and not the default network). None except for Plex are set to use Host.

    I have removed Plex again and added it once more to the docker. Unfortunately Plex logs are still showing the same issue.








  • Interesting idea, I’ve never done this before. I tried opening the console from within the sonarr portainer container. That failed with “unable to retrieve image details”

    On searching this, I was able to connect using:

    sudo docker exec -it sonaar bash

    This put me at the root of the container, and from there, I could navigate through:

    root@xx:/data/torrents/rtorrent/Completed/tv-sonarr

    From there I could see the file. But the permissions were for user abc and group “users”. But I found the same when I browsed to the usenet downloads area, so I think this is more because of the way I logged in to root. I don’t have any issues with usenet and sonaar. ID from there shows my uid as 0 and gid 0



  • I don’t think the issue is the volume because sonarr is finding my usenet downloads.

    The actual folder structure is /data/usenet/download. sonarr is given the volume mount: /data
    It gets the download location from SAB. All works fine.

    Equating this to my situation, I am expecting the folder mapping to put the download in the location /data/torrents/rtorrent etc Again this matches the info sonarr receives from rutorrent. And the volume mount /data should be allowing access same as it gets to the usenet folders.