Hello everyone,

I recently started my journey of using Proxmox for self hosting and boy is it very satisfying, I learned a lot along the way so far and have yet to learn some more. So once again, I am asking for help if you could so kind to offer it.

I have a privileged CT running Debian that has Fuse enabled. I have it setup to rclone mount a drive within the CT and all is working fine and dandy.

What I have been trying to do is to make that mount visible on the host such that another CT can access it and read the contents of the mount.

The thought is I can have the rclone CT mount the drive, and then have the Plex CT read that drive and scan it for content.

I tried to do a bind mount point but the fuse mount doesn’t seem to be visible to the host (and hence, not visible to Plex either)

Am I missing something? Is it even possible? Any other suggestions or workarounds.

Thank you in advance

  • mlfh@lemmy.sdf.orgEnglish
    5·
    2 days ago

    The rclone fuse mount is essentially running in the memory of the container, and doesn’t translate back into the filesystem that the host presents from itself into that container.

    Since rclone is available in the debian repos, the simplest and easiest option would be to do the rclone mount on the host and then pass that via bind mounting into the Plex container.

    If you want to keep the rclone mounting containerized though (or if your Proxmox host is clustered, you want to mount it on the host, and you want the mount to be shared between your nodes), you can use rclone’s experimental but built-in nfs server feature: https://rclone.org/commands/rclone_serve_nfs/

    Make sure your 2 containers can talk to each other over a secure network (“this server does not implement any authentication so any client will be able to access the data”), start the nfs server in the rclone container, and mount it via nfs in the Plex container.

    Good luck!

    • modeh@piefed.socialOPEnglish
      3·
      1 day ago

      That explains quite a lot, thank you for elaborating on it. I am trying to keep the host as minimal as possible, that’s why I’m avoiding doing the mount directly on it and instead containerizing everything.

      I will give the rclone NFS approach a shot, it’s definitely a worthwhile option.

      • erock@lemmy.mlEnglish
        1·
        22 hours ago

        I went down a similar path as you. The entire proxmox community argues making it an appliance with nothing extra installed on the host. But the second you need to share data — like a nas — the tooling is a huge pain. I couldn’t reliably find a solution that felt right.

        So my solution was to make my nas a zfs pool on my host. Bind mounting works for CTs but not VMs which is an annoying feature asymmetry. So I decided to also install an nfs server that exposed my nas.

        I know that’s not what you want but just wanted to share what I did.

        The feature asymmetry between CTs and VMs basically made CTs not part of my orchestration.