this post was submitted on 26 Sep 2025
11 points (86.7% liked)

Selfhosted

51836 readers
602 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

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

you are viewing a single comment's thread
view the rest of the comments
[–] erock@lemmy.ml 1 points 1 day ago* (last edited 1 day 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.