Comment on Am I corrupting my data?

• Cyber@feddit.uk ⁨1⁩ ⁨day⁩ ago

  I always prefer bare metal for the core NAS functionality. There’s no benefit in adding a hypervisor layer just to create an NFS / SMB / iSCSI share

  OMV comes with it’s own bare metal installer, based on Debian, so it’s as stable as a rock.

  If you’ve used it before, you’re probably aware that it needs it’s own drive to install on, then everything else is the bulk storage pool… I’ve used various USB / mSATA / M.2 drives over the years and found it’s a really good way to segregate things.

  I stopped using OMV when - IMO - “core” functions I was using (ie syncthing) became containers, because I have no use for that level of abstraction (but it’s less work for the OMV dev to maintain addons, so fair enough)

  So, you don’t have to install docker, OMV automatically handles it for you.

  How much OMV’s moved on, I don’t know, but I thought it would simplify your setup.

  source

  • thelemonalex@lemmy.world ⁨7⁩ ⁨hours⁩ ago

    Okay, thank you, that’s good to know. However, I don’t have two separate devices that I can use to separate the NAS functionality from the Docker functionality, that’s why I was using Proxmox in the first place. And, I’m not sure how well Docker can run in OMV. But I’ll still keep it in mind as an option, thank you!

    source

    • Cyber@feddit.uk ⁨12⁩ ⁨minutes⁩ ago

      I think you’ve misunderstood

      Ok, OMV needs a separate (small) boot drive to install on (ie consider a M.2 / SSD on a USB adapter)

      But, then all your (large) storage is used for the NAS.

      OMV will run Docker containers, but their data would also be pointed to the large NAS storage.

      |  Small |     Large   |
      |-----------+----------------|
      | OMV   | Files         |
      | Docker| Data, etc |
      

      source