Comment

giacomo@lemm.ee ⁨1⁩ ⁨year⁩ ago

proxmox is awesome, but i dont think its a right fit for what you’re looking to do. if you just want to run a few podman containers, I’d probably go with a server os that is geared towards containers.

check out fedora’s coreOS or maybe ucore from the universal blue project. it seems like they’re both good candidates for podman. i think opensuse has a similar offering in microOS.

i recently migrated containers from an older Ubuntu server running docker to a ucore server with mainly rootless podman containers. i think I prefer ucore as updates are automated, reboots are scheduled for off hours, and the podman containers are kept updated by systemd service. and cockpit comes on the os image container, so i can poke stuff on a webpage too I guess.

source

Sort:hotnew top

pfr@lemmy.sdf.org ⁨1⁩ ⁨year⁩ ago
Do you recommend ucore or ucore-minimal?

source
- giacomo@lemm.ee ⁨1⁩ ⁨year⁩ ago
  Haha, you’re not wrong about it seeming a little extra to get installed.
  
  I used coreos live ISO and coreos-installer with the ignition file produced from a ucore-autorebase.butane file. I lightly edited the example butane file with the ssh keys I wanted to use, password hash, and “ucore-minimal:stable-nvidia” since I’ve got an old 1060 gpu in the server for jellyfin.
  
  source
pfr@lemmy.sdf.org ⁨1⁩ ⁨year⁩ ago
Thanks for this. I went down a bit of a rabbit hole today looking into proxmix, and started thinking that a Dell optiplex won’t cut it after reading how using proxmox with zfs uses more resources, plus I kept seeing people recommend ECC ram which is more expensive and is harder to come by.

I’m look at ucore, but most install instructions for things are targeted at debian systems using apt. I guess that’s not a major hurdle though.

Proxmox still peaks my interest, and maybe one-day when I can afford a decent setup I’ll get into it some more.

source
- klangcola@reddthat.com ⁨1⁩ ⁨year⁩ ago
  Some key points regarding Proxmox:
  
  Even if you only want to run two services, you still want to keep them isolated. This can save you much pain and frustration in the future when they require upgrades
  
  Proxmox let’s you easily manage VM and LXC containers. So you can easily manage backups, or spinning up a separate test instance of your service. Which again, can save you pain and frustration when it comes to future updates of your services.
  
  Backups are even better if you can deploy the separate Proxmox Backup Server
  
  Should you ever want to add another service in the future, you can test it out in a new VM or container without it affecting your existing services at all
  
  ZFS is indeed quite memory hungry, but AFAIK it’s mainly used for the read cache, and can be tuned to use less RAM at the cost of performance
  
  ZFS is mentioned a lot because it’s good, but Proxmox also supports a range of other storage technologies: LVM, mdraid, EXT4, CEPH
  
  Proxmox is just standard Debian and KVM/QEMU virtual machines under the hood. Which means you can use standard tooling and workflow should you need it for some edgecase.
  
  You mentioned Jellyfin in a container: My understanding is that Jellyfin in Docker has some extra limitations or complexities when it comes to hardware encoding.
  
  Jellyfin also has official documentation for how to deploy in LXC container and get HW transcoding working (Less complex than in Docker).
  
  LXC containers are not like Docker containers. While a Docker container is meant to be an immutable image of a (single) application, LXC is more like a full fledged VM, but without the overhead of virtualization. LXC containers are full systems, and you install software via the usual apt, dnf etc
  
  The “correct” way to run Docker in Proxmox is to run Docker in a Virtual machine. Installing Docker inside a LXC container is also possible, with some caveats. Installing Docker directly on the Proxmox host is not recommended
  
  For reference, my oldest Proxmox server is a 2013 AMD dualcore 16GB DDR2 ram with VMs on LVMthin on a single SSD, with legacy VM doing mdraid of 3 HDDs using hardware passthrough. Performance is still OK, the overhead from Proxmox is negligible compared to strain from the actual workloads
  
  source