Proxmox vs. Debian: Running media server on older hardware

[jlh@lemmy.jlh.name]

yeah, and qemu and lxc are very much legacy at this point. Stick with docker/podman/kubernetes for containers.

[darcmage@lemmy.dbzer0.com]

None of your listed use cases will even come close to taxing the 6600k. It's going to probably sit happily in idle states most of the time.

Proxmox also has great snapshotting and backup features. Makes it easier to mess around with your containers/VMs without worrying too much.

[sugar_in_your_tea@sh.itjust.works]

Agreed.

I run podman w/ rootless containers, and it works pretty well. Podman is extra nice in that it has decent suppor for kubernetes, so there's a smooth transition path from podman -> kubernetes if you ever want/need it. Docker works well too, and docker compose is pretty simple to get into.

[mhzawadi@lemmy.horwood.cloud]

right tool for the job mate, not everything works great in a container.

Also Proxmox is not legacy as its used a lot in homelabs and also some companys

I use proxmox to carve up my dedicated host with OVH, 3 of the vms run docker anyway.

[mhzawadi@lemmy.horwood.cloud]

would agree the hardware would run everything fine

[jlh@lemmy.jlh.name]

Yeah, Kubernetes is more automated and expandable, but docker compose has a ton of good examples and it's really easy to get into as a beginner.

[jlh@lemmy.jlh.name]

I'm not saying it's bad software, but the times of manually configuring VMs and LXC containers with a GUI or Ansible are gone.

All new build-outs are gitops and containerd-based containers now.

For the legacy VM appliances, Proxmox works well, but there's also Openshift virtualization aka kubevirt if you want take advantage of the Kubernetes ecosystem.

If you need bare-metal, then usually that gets provisioned with something like packer/nixos-generators or cloud-init.

[sugar_in_your_tea@sh.itjust.works]

Kubernetes is also designed for clustered workloads, so if you are mostly hosting on one or two machines, YAGNI applies.

I recommend people start w/ docker compose due to documentation, but I personally am switching to podman quadlets w/ rootless containers.

[geography082@lemm.ee]

Promox runs on debian. But anyway you will be surprised about proxmox can run in limited hardware. I have it running in a garbage mini PC and an old notebook

[mhzawadi@lemmy.horwood.cloud]

Yes, but no. There is still a lot of places using old fashioned VMs, my company is still building VMs from an AWS ami and running ansible to install all the stuff we need. Some places will move to containers and that's great, but containers won't solve every problem

[ferawyn@lemmy.world]

Proxmox is Debian.
I do always suggest installing Debian first, and then installing Proxmox on top. This allows you to properly set up your disks, and networking as needed, as the Proxmox installer is a bit limited: https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_12_Bookworm
Once you have it up and running, have a look at the CT Templates. There's a whole set of pre-configured templates from TurnkeyLinux (again, debian+) that make it trivial to set up all kinds of services in lightweight LXC Containers.

[possiblylinux127@lemmy.zip]

ZFS is probably what you want

[possiblylinux127@lemmy.zip]

I would just install Proxmox since it is way easier

Also last time I checked the Debian installer didn't support ZFS

[possiblylinux127@lemmy.zip]

What are you going to run containers on? You need VMs to power everything.

[possiblylinux127@lemmy.zip]

You are going to what, install Kubernetes on every node?

It is far easier and more flexible to use VMs and maybe some VM templates and Ansible.

[Guest]

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?

[Guest]

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

[Guest]

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.