Proxmox vs. Debian: Running media server on older hardware

[irmadlad@lemmy.world]

I do always suggest installing Debian first, and then installing Proxmox on top.

Correct me if I'm wrong, but isn't Proxmox it's own OS unto itself? What would be the advantage of installing Proxmox 'on top of' Debian when it's Debian already as you pointed out?

[irmadlad@lemmy.world]

OP, I'm running Proxmox on and old Dell T320 /32gb RAM. I am not having any real issues doing so. I run Docker and a handful of Docker containers. I'm really not into the arr stack, but I wouldn't think you'd have much issue.

[lka1988@lemmy.dbzer0.com]

Why would you install a GUI on a VM designated to run a Docker instance?

You should take a serious look at what actual companies run. It's typically nested VMs running k8s or similar. I run three nodes, with several VMs (each running Docker, or other services that require a VM) that I can migrate between nodes depending on my needs.

For example: One of my nodes needed a fan replaced. I migrated the VM and LXC containers it hosted to another node, then pulled it from the cluster to do the job. The service saw minimal downtime, kids/wife didn't complain at all, and I could test it to make sure it was functioning properly before reinstalling it into the cluster and migrating things back.

[tofu@lemmy.nocturnal.garden]

You have some options that aren't in the installer e.g. full disk encryption

[irmadlad@lemmy.world]

hmmmm. Wouldn't you have to remove the Debian kernal and use the Proxmox kernal? Sorry, not trying to be obtuse, I just have never installed Proxmox 'on top' of Debian. I always opted for the clean install.

[jlh@lemmy.jlh.name]

Yes.

It is not easier to use Ansible. My customers are trying to get rid of Ansible.

[jlh@lemmy.jlh.name]

I'm a DevOps/ Platform Engineering consultant, so I've worked with about a dozen different customers on all different sorts of environments.

I have seen some of my customers use nested VMs, but that was because they were still using VMware or similar for all of their compute. My coworkers say they're working on shutting down their VMware environments now.

Otherwise, most of my customers are running Kubernetes directly on bare metal or directly on cloud instances. Typically the distributions they're using are Openshift, AKS, or EKS.

My homelab is all bare metal. If a node goes down, all the containers get restarted on a different node.

My homelab is fully gitops, you can see all of my kubernetes manifests and nixos configs here:

https://codeberg.org/jlh/h5b

[jlh@lemmy.jlh.name]

Yes, it's fine to still have VMs, but you shouldn't be building out new applications and new environments on VMs or LXC.

The only VMs I've seen in production at my customers recently are application test environments for applications that require kernel access. Those test environments are managed by software running in containers, and often even use something like Openshift Virtualization so that the entire VM runs inside a container.

[jlh@lemmy.jlh.name]

Yeah, definitely true.

I'm a big fan of single-node kubernetes though, tbh. Kubernetes is an automation platform first and foremost, so it's super helpful to use Kubernetes in a homelab even if you only have one node.

[jlh@lemmy.jlh.name]

I dont have any VMs running in my homelab.

https://codeberg.org/jlh/h5b

Most of my customers run their Kubernetes nodes either on bare metal, or on a cloud provisioned VM from AWS/GCP/Azure etc

[sugar_in_your_tea@sh.itjust.works]

What's so nice about it? Have you tried quadlets or docker compose? Could you give a quick comparison to show what you one like about it?

[marauding_gibberish142@lemmy.dbzer0.com]

Not calling you out specifically OP, but can someone tell me why this is a thing on the internet?

multiple 12GB drives

GB??? I assume TB automatically when people say this but it still is a speedbreaker when I'm thinking about the post.

[marauding_gibberish142@lemmy.dbzer0.com]

QEMU is legacy? Pray tell me how you're running VMs on architectures other than x86 on modern computers without QEMU

[marauding_gibberish142@lemmy.dbzer0.com]

Sometimes, VMs are simply the better solution.

I run a semi-production DB cluster at work. We have 17 VMs running and it's resilient (a different team handles VMWare and hardware)

[glizzyguzzler@lemmy.blahaj.zone]

I’m surprised no one’s mentioned Incus, it’s a hypervisor like Proxmox but it’s designed to install onto Debian no prob. Does VMs and containers just like Proxmox, and snapshots too. The web UI is essential, you add a repo for it.

Proxmox isn’t reliable if you’re not paying them, the free people are the test people - and a bit back there was a bad update they pushed that broke shit. If I’d have updated before they pulled it, I’d have been hosed.

Basically you want a device that you don’t have to worry about updates, because updates are good for security. And Proxmox ain’t that.

On top of their custom kernel and stuff, it’s just less eyes than, say, the kernel Debian ships. Proxmox isn’t worth the lock-in and brittleness for just making VMs.

So to summarize, Debian and Incus installed. BTRFS if you’re happy with 1 drive or 2 RAID 1 drives. BTRFS gets scrubbing and bitrot detection (protection with RAID 1). ZFS for more drives. Toss on Cockpit too.

If you want less hands-on, do to OpenMediaVault. No room for Proxmox in my view, esp. for no clustering.

Also the iGPU on the 6600K likely is good enough for whatever transcoding you’d do (esp. if it’s rare and 1080p, it’ll do 4k no prob and multiple streams at once). The Nvidia card is just wasting power.

[catloaf@lemm.ee]

Some of us don't build applications, we use them as built by other companies. If we're really unlucky they refuse to support running on a VM.

[jlh@lemmy.jlh.name]

Not QEMU in particular, poor phrasing on my part. I just mean setting up new environments that run applications on VMs.

[marauding_gibberish142@lemmy.dbzer0.com]

I prefer some of my applications to be on VMs. For example, my observability stack (ELK + Grafana) which I like to keep separate from other environments. I suppose the argument could be made that I should spin up a separate k8s cluster if I want to do that but it's faster to deploy directly on VMs, and there's also less moving parts (I run two 50 node K8S clusters so I'm not averse to containers, just saying). Easier and relatively secure tool for the right job. Sure, I could mess with cgroups and play with kernel parameters and all of that jazz to secure k8s more but why bother when I can make my life easier by trusting Red Hat? Also I'm not yet running a k8s version that supports SELinux and I tend to keep it enabled.

[jlh@lemmy.jlh.name]

Sure!

I haven't used quadlets yet, but I did set up a few systemd services for containers back in the day before quadlets came out. I also used to use docker compose back in 2017/2018.

Docker compose and Kubernetes are very similar as a homelab admin. Docker compose syntax is a little less verbose, and it has some shortcuts for storage and networking. But that also means it's less flexible if you are doing more complex things. Docker compose doesn't start containers on boot by default I think(?) which is pretty bad for application hosting. Docker-compose has no way of automatically deploying from git like ArgoCD does.

Kubernetes also has a lot of self-healing automation, like health checks that can either disable the load balancer and/or restart the container if an app is failing, automatic killing of containers when resources are low, preventing the scheduling of new containers when resources are low, gradual roll-out of containers so that the old version of a container doesn't get killed until the new version is up and healthy (helpful in case the new config is broken), mounting secrets as files in a container, and automatic retry on failed containers.

There's also a lot of ubiquitous automation tools in the Kubernetes space, like cert-manager for setting up certificates (both ACME and local CA), Ingress for setting up reverse proxy, CNPG for setting up postgres clusters with automated backups, and first-class instrumentation/integration with prometheus and loki (both were designed for kubernetes first).

The main downsides with Kubernetes in a homelab is that there is about a 1-2GiB RAM overhead for small clusters, and most documentation and examples are written for docker-compose, so you have to convert apps into a Deployment (you get used to writing deployments for new apps though). I would say installing things like Ingress or CNPG is probably easier than installing similar reverse-proxy automations on Docker-compose, though.

[jlh@lemmy.jlh.name]

Yeah, that's fair. I have set up Openshift Virtualization for customers using 3rd party appliances. I've even worked on some projects where a 3rd party appliance is part of the original spec for the cluster, so installing Openshift Virtualization to run VMs is part of the day 1 installation of the Kubernetes cluster.