I have a trusty UnRaid server that has been running great for almost 3 years now, with some kinks and headaches here and there, but mostly very stable. Now I’m entertaining the idea of setting that box up with ProxMox, and running UnRaid virtualized. The reason being that I want to use UnRaid exclusively as a NAS and then run all dockers and VMs on ProxMox (at least that’s how I’m picturing it). I would like to know your opinion on this idea. All I have is Nextcloud, Immich, Vaultwarden, Jellyfin, Calibre, Kavita and a Windows VM I use to update some hardware every now and then. I mainly want to do that for the backup capabilities in ProxMox for each instance. Storage is not a concern, and I have 64GB of ECC Ram running in that box. What are the Pros and Cons, or is it even worth it to move all this to ProxMox?

  • NullGator@lemmy.ca
    link
    fedilink
    English
    arrow-up
    11
    ·
    7 months ago

    If you virtualize unraid, unraid wont have direct drive access - you can get around this by getting an HBA card and forwarding that to the unraid VM. Others have mentioned that proxmox doesn’t have docker support, I personally run docker containers within lxc boxes on proxmox. There are solutions to make managing containers easier, like portainer, if you want to go down that route.

    • youmaynotknow@lemmy.mlOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      7 months ago

      After Ai watched Lempa’s video virtualizing TrueNAS passing through all drives on ProxMox, I started searching to see if anyone had tried the same with UnRaid, and TechHut actually did it.

      https://www.youtube.com/watch?v=ahOXQM4416Q

      However, my use case is somewhat different than his, and he’s just a hobbyist like me, so I’m much more comfortable asking in this community where it’s highly likely that someone already crashed and burned before me, lol.

      I’m thinking I’ll take the advise of just building a new server for ProxMox, and then use my current UnRaid box exclusively for storage. That should be somewhat safer, right?

      • NullGator@lemmy.ca
        link
        fedilink
        English
        arrow-up
        2
        ·
        7 months ago

        That’s my current configuration, it works well. Put your storage on a separate network. I use smb shares so my data is password protected, even on that separate network.

        Main downside of this is there’s more places for failure to occur. If your NAS goes down, there’s no storage access for proxmox which may cause service downtime. Alternatively if proxmox goes down, this also causes service downtime. For me this is fine, but something to keep in mind. Ideal solution would be 2 HA clusters for storage and compute, but thats expensive haha.

    • fishpen0@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      2
      ·
      7 months ago

      Run docker within lxc within proxmox. This gave me an aneurism. You’ve lost the whole point of not actually virtualizing with containers by putting in two layers deep in virtualization. At this point your shit is so convoluted why don’t you just run kubernetes

      • NullGator@lemmy.ca
        link
        fedilink
        English
        arrow-up
        2
        ·
        7 months ago

        How is running a container in an LXC worse than in a VM? It’s not really, is it? No, not really. Kubernetes could also be built on top of the LXC as well, sure. There are a number of genuine benifits from running docker on top of an LXC, and it doesn’t compromise security or come with a significant performance drop (unlike VMs).

        • fishpen0@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          7 months ago

          I was suggesting to do neither and run the container directly. Putting k8s on top of lxc is still completely stupid. Just run k8s bare metal to operate your containers.