Hello everyone,
I finally managed to get my hands on a Beelink EQ 14 to upgrade from the RPi running DietPi that I have been using for many years to host my services.
I have always was interested in using Proxmox and today is the day. Only problem is I am not sure where to start. For example, do you guys spin up a VM for every service you intend to run? Do you set it up as ext4, btrfs, or zfs? Do you attach external HDD/SSD to expand your storage (beyond the 2 PCIe slots in the Beelink in this example).
I’ve only started reading up on Proxmox just today so I am by no means knowledgeable on the topic
I hope to hear how you guys setup yours and how you use it in terms of hosting all your services (nextcloud, vaultwarden, cgit, pihole, unbound, etc…) and your ”Dos and Don’ts“
Thank you 😊
I recommend you use containers instead of VMs when possible, as VMs have a huge overhead by comparison, but yes. Each service gets its own container, unless 2 services need to share data. My music container, for example, is host to both Gonic, slskd and Samba.
I wouldn’t do that as it complicates things unnecessarily. I would just run a container runtime inside LXC or VM.
There is barely any overhead with a Linux VM, a Debian minimal install only uses about 30MB of RAM! As an end user i find performance to be very similar with either setup.
Containers as in LXC?
Correct.
Side note- people will tell you not to put dockers in an LXC but fuck em. I don’t want to pollute my hypervisor with docker’s bullshit and the performance impact is negligeable.
I wouldn’t recommend running docker/podman in LXC, but that’s just because it seems to run better as a full VM in my experience.
No sense running it in the hypervisor, agreed.
LXC is great for everything else.
There are dozens of us!
Not at all. The benefits outweighs the slight increased RAM usage by a huge margin.
I have Urbackup running in a dietpi VM. I have it set for 256mb of RAM. That includes the OS and the Urbackup service. It works perfectly fine.
I have an alpine VM that runs 32 docker containers using about 3.5GB of RAM. I wouldn’t call that bloat by any means.
A fresh Debian container uses 22 MiB of RAM. A fresh debian VM uses 200+ MiB of RAM.
A VM has to translate every single hardware interaction, a container doesn’t.
I don’t want to fuck flies about the definition of ‘huge’ with you, but that’s kind of a huge difference.
Translate? You know that a CPU sits idle most of the time right?
What kind of potato are you running? Also, how many hundred services do you run on it anyway, complaining about 200mb. You better off running docker on baremetal, if you are that worried.
Do you know how much RAM Windows 11 uses on idle?
WTF