• entropicdrift@lemmy.sdf.org
    link
    fedilink
    English
    arrow-up
    3
    ·
    2 days ago

    Hard links are a built-in feature of basically every modern filesystem. The bigger question to me is, why aren’t hard links working for you?

    • flightyhobler@lemm.eeOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      2 days ago

      There needs to be an overlap in the mount points of docker jellyfish and docker sonarr, etc. I don’t think I got it right. Besides, sonar ends up not moving the series inside the tv shows folder, leaving the episodes outside, in the media folder above. If I knew exactly what was going on I would fix it. Last time I dealt with it was ages ago, so perhaps I can do it now.

      • tux7350@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        7 hours ago

        The over lap of docker containers needs to happen from inside the perspective of the container. If you send Radarr to pull a movie from bittorrent, they both need to “be in the same spot”. If bittorrent thinks it’s saving a movie to /data/torrent then Radarr also needs to see the movie at /data/torrent.

        That’s why so many guides use the /data/ label scheme. Its just easy to use and implement. Side note, for hard links to work, all the folders need to be on the same drive. Can’t hard link between different drives.

        • flightyhobler@lemm.eeOP
          link
          fedilink
          English
          arrow-up
          1
          ·
          6 hours ago

          This was the crux of my confusion, but after a couple of years of Docker, it now makes more sense to me 😁