Hi all. I was curious about some of the pros and cons of using Proxmox in a home lab set up. It seems like in most home lab setups it’s overkill. But I feel like there may be something I’m missing. Let’s say I run my home lab on two or three different SBCs. Main server is an x86 i5 machine with 16gigs memory and the others are arm devices with 8 gigs memory. Ample space on all. Wouldn’t Proxmox be overkill here and eat up more system resources than just running base Ubuntu, Debian or other server distro on them all and either running the services needed from binary or docker? Seems like the extra memory needed to run the Proxmox software and then the containers would just kill available memory or CPU availability. Am I wrong in thinking that Proxmox is better suited for when you have a machine with 32gigs or more of memory and some sort of base line powerful cpu?

  • glizzyguzzler
    link
    fedilink
    English
    arrow-up
    7
    ·
    5 months ago

    Incus is way easier to work with than Proxmox, and it sits on your OS of choice instead of being the OS you must use. For home use it’s way easier to use with the web ui, it even has clustering if you want to go hard.

    So you can install Incus when you want a VM/LXC container and not have to commit to a VM/LXC container OS from the start.

    Also Proxmox free just had a bad update that björked some stuff if you updated when it was live. Proxmox free is rolling and apparently lacks basic sanity checks for updates.

    • rottedmood@lemmy.linuxuserspace.showOP
      link
      fedilink
      English
      arrow-up
      3
      ·
      5 months ago

      i played around with Incus yesterday on one of my VPSs that I really don’t care about. I did find it really interesting. But im just wondering if its still a bit too much for what i use my home lab for (running local services like jellyfin, gitea, etc.). I would prefer to containerize all of those, but unless im misunderstanding something somewhere (and I probably am), running Incus to then run another instances of ubuntu 22.04 (or whatever) so i can set up Jellyfin or Gitea inside of that seems like a bit of overkill. However, as im trying to get nextcloud set up and running, having it exposed to the internet would mean spousal factor would go way up. Honestly they are about to kill me for using pihole, so having them have to turn on tailscale to connect to nextcloud, well sometimes it feels like its asking too much. So this is where running something in an isolated container would make me feel a bit more at ease. ah if only my spouse would just learn to turn on tailscale when they need it, but i don’t see that happening any time soon.

      • glizzyguzzler
        link
        fedilink
        English
        arrow-up
        1
        ·
        5 months ago

        I do use it to hold internet-exposed things in LXC containers to sidestep having to figure out how to not run things as Docker root.

        You do not need it for everything, but since it’s not an OS that makes it your everything, that’s ok! Run Docker containers as you need, put internet-exposed ones in an LXC container, put home assistant in a VM because it’s special.

    • Lemongrab@lemmy.one
      link
      fedilink
      English
      arrow-up
      3
      ·
      5 months ago

      I remember updating (maybe a year ago now) and it making all my containers unaccessable.

      • glizzyguzzler
        link
        fedilink
        English
        arrow-up
        1
        ·
        5 months ago

        Incus or Proxmox (e.g., should I shift to Incus LTS or something?)

        • Lemongrab@lemmy.one
          link
          fedilink
          English
          arrow-up
          2
          ·
          5 months ago

          If incus works for yoy, use it. Proxmox locks you out of the option to choose your base server distros.

          • glizzyguzzler
            link
            fedilink
            English
            arrow-up
            1
            ·
            5 months ago

            Ah, I was wondering which one you updated and it made your containers inaccessible!

            • Lemongrab@lemmy.one
              link
              fedilink
              English
              arrow-up
              2
              ·
              5 months ago

              Sorry, misunderstood. Proxmox Free broke my containers on updating a while ago.

              Now I use Docker-style application containerizing, but I think LXC (the base technology powering Incus/LXD) is useful in a number of situations and perfectly viable for use. I think Incus-containerized applications are easier to upgrade individually (like software updates of your apps, no need to recreate the container image) and gives a closer to native experience of managing. You do lose out on automated deployment of applications from widely available image sources like docker.io, but the convenience-loss is minimal.

              • glizzyguzzler
                link
                fedilink
                English
                arrow-up
                2
                ·
                5 months ago

                Good to know Proxmox’s bad updates are more pervasive than the latest bad update.

                I have been able to install Docker in the LXC containers and pull images in with the normal commands. I do that container-in-container to get effectively rootless docker containers for stuff that I couldn’t figure out how to run rootless. So you don’t even lose out on docker if you’re determined! And as you said incus goes on any OS, you can docker just fine on the base OS of your choice and use incus for specific things!