With that said, I’ve recently I’ve started using Arch for a couple of machines. Yes I know that’s a solvable problem, but at that point it damages stability. I’d prefer to be able to use Alpine for a number of these, but the lack of glibc makes running some things much more annoying. Most of the machines I run are based on Debian, because it’s a simple, lightweight distribution with decent package support. There are still places however where it’s either easier to run VMs, or I have no choice. Wherever possible, I try and run LXC containers over VMs, because of the lower overhead and easier to manage resources. With LXC, if you want to access some storage on the host, just bind mount it in with almost 0 overhead - No PCI passthrough necessary. Because LXC processes use the same kernel, it means sharing access to things like GPUs and storage is significantly easier, and with less overhead. Because of the shared kernel, LXC containers are constrained to only being Linux, but they can be any distribution you want. Think of them like a fancy chroot or Docker container (they’re not, but just think about it). LXC containers share the same kernel, resulting in dramatically less overhead and thus greater performance compared to VMs. LXC on the other hand is very different, and yet fairly similar. There is support for passing through single HDDs, but I wouldn’t recommend it. Because they’re entirely separate, devices such as GPUs, drives or USB controllers have to be passed in entirely. The downside is that because it’s an entirely separate OS, there’s some additional overhead. Because it’s virtualized, it means you can run practically any OS (yes, even macOS in theory) in a VM, completely isolated from the host OS. It’s a separate OS and a completely separate kernel. VMs are virtual machines which you’re probably already used to, powered by QEMU. Proxmox lets you create 2 types of virtualized runtime (I’m just going to refer to them as “machines” because it’s much easier): VMs and LXC - Each with their own pros and cons.
#OLDER VERSIONS OF DELUGE FOR MAC FREE#
All things which I’ve found annoying to set up in the past, but come free with Proxmox. It’s Debian based, so it’s lightweight, but it also comes packaged with a modern version of ZFS, and extra configuration around cron emailing and ZFS event daemon. This ability to run multiple isolated “machines” also means applications and environments can be better isolated from each other, and their base OS’s selected and tuned perfectly.Īs an OS in itself, Proxmox is also really nice. It’s incredibly simple to spin up a test VM or LXC to start playing around with something. One of the biggest benefits of Proxmox is that it’s a hypervisor. Unfortunately as you scale, it can get more annoying and limiting. This worked absolutely fine, and for a first-timer that’s still the approach I’d recommend. Ubuntu server base OS, running Docker containers for everything. So, here goes… # “Why not just Docker all the things on the host?”īefore Proxmox, that’s exactly what I did. I’ve had quite a few people ask exactly how I’ve set up Proxmox, and the decisions behind it. Therefore, there’s a huge amount of scope for opinions, lessons and customizations. Being a hypervisor OS, it makes sense to run everything in VMs or LXC containers, not on the host. Back in December, I fully rebuilt my home server from the ground up based on Proxmox.
0 kommentar(er)
