Proxmox bare metal vs debian reddit Tried Proxmox with both the stock 5. vmdk file to the right proxmox vm directory, add the disk ( not convert/import ) to the vm, and set it as the boot volume. The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway. The bigger machine runs proxmox for virtualization. I'd say that Ubuntu LTS is probably the closest for the bare metal. (Its very, VERY small, and extremely stripped down to the bare minimum) For personal use, I would choose Manjaro. I do this whether it’s my on premise servers or my VPS in someone’s cloud. When installed in a Proxmox VM, this control is best achieved using and HBA and PCI Passthrough, which must be supported by both the motherboard and the CPU. Using kvm vms for pihole and windows domain controllers Using samba for windows shares. It CAN work, but you add multiple points of failure by virtualising your NAS vs making it bare metal. It's not really a Linux distribution since your not using the os whatsoever, it's so minimal that it's considered itself a type 1 hypervisor. Yes virtualization adds overhead, and I know that. I’ve landed on bare metal Linux for my main production and that hosts all my apps that I want to be simple to fix and maintain. I'll be running a bunch of Windows and Linux VMs, Plex and associated services. I then followed this tutorial: Installing Home Assistant Supervised on Debian 10 I run a small VM for HA only 4GB of memory and 20GB of storage, and I have an Ubuntu server also on Proxmox that has my MariaDB for recorder, Infux, Grafana, Postgreql Bare-metal vs Proxmox I'm in the process of building my homelab upgrade from a separate QNAP NAS and server to a dedicated rack server (probably a Dell R520 or 720). 2 months later I’m wishing I went with my old setup of Ubuntu (actually would do Debian or alpine, etc) running docker and kvm. The 2 main benefits I see are: Easy reinstall of the VM if it crashes for some reason or if I want to change the OS to something else. I also have proxmox installed on a different server. Proxmox is not a hypervisor. Proxmox install and Docker into same hp mini and 60 watt Cpu:) Docker on Server Node -> Should be no go. Proxmox does add complexity but also allows more flexibility and can be a bit safer, as you can have serperate systems etc. If you choose to stay on proxmox, you can create a LXC and run docker. We think our community is one of the best thanks to people like you! Proxmox is that minimal OS that gives you most of the things an OS would give you but without the extra "stuff" a full blown OS brings, which in theory frees up more resources for allocation. The problem you’re running into is likely just with the display modes for the installer, so if the Debian one works then go for it. PVE #1 backs up a CT, PVE #2 restores the CT. Personally I wouldn't do either of those, but that's your call. I do not fully understand though if this is going to have some major drawbacks vs using the proxmox iso? If you plan to run for example frigate in HAOS with a coral - don't. With proxmox you get the same concept as Docker on Ubuntu, but with an extra layer that allows for repeatable, and recoverable operations. Crashplan on bare metal on storage server Has been stable for me. It has two vms right which are part of k3s cluster. Essentially, you run Frigate in a docker container ideally on bare metal Linux. I ran it for a while on an LXC container on proxmox, but struggled with USB passthrough and decided to go back to bare metal. In summary, I prefer Proxmox over TrueNAS Core because the harder part of a hyperconverged server is the compute part, and Proxmox makes that easier. It's fun to learn, makes backup/management of that VM/LXC easy, and makes any future experimenting you want to do super easy as well. They supposedly have better multi-cluster management with xen-orchestra, but again not many are running multiple clusters at this part of reddit. Jan 15, 2021 · As a Proxmox/HA OS sceptic I have been very happy with Debian + Supervised install. Docker On VM -> Easy and recommended. But a Google coral through proxmox is not a good idea. I have a bare metal Rocky Linux server that runs most of my containers and a few bare metal solutions. Super easy migration. So the baremetal Installation ist the thing that worked for me. I had nothing but issues with it. Bare Metal. Debian is amazing because of the community same with deb based Ubuntu. Enterprise Proxmox: Install Plex LXC with HW Transcoding/HDR Tone Mapping - Derek Seaman's Tech Blog [SOLVED] - LXC i9-12900T GPU Plex passthrough | Proxmox Support Forum. TrueNAS has a minimum requirement of 8 GB and Proxmox itself needs 2 GB JUST for the OS. I use the smaller machine for anything bare metal. For example. With a Proxmox VM you will have to shut the VM down, go to the proxmox UI, assign the stick to the VM and boot it back up. Load Truenas Scale as a VM in Proxmox. that is a good idea. straight from the mini PC with the HDMI port). Proxmox itself has very little overhead, plus you can run portainer in a very light-weight LXC rather than a fully fledged VM. If you are not thinking of using Proxmox in this way - you really should start over and install a Linux dist (debian/ubuntu/etc. I think, if trying to use the keyboard on the PVE server itself, I still need a desktop on PVE, or are you saying I could boot directly into the one VM that is my main driver, such that I get all the local connected harware and every We would like to show you a description here but the site won’t allow us. This is nice because proxmox is a excellent backup and vm movement solution, you can setup nightly backup to a NFS share on a Nas super easy. It’s still running on “bare metal” and ends up being effectively the same in the end albeit without the Proxmox distro logos and boot screen etc. I run a 3-node PVE cluster at home plus a bare-metal PBS host. . " proxmox option 2. Proxmox is just a Debian machine pre-configured to run VMs. Visual We would like to show you a description here but the site won’t allow us. A Debian 11 CT uses less than a 100MB memory and extremely low cpu usage after installing pihole. Proxmox is meant to be deployed on bare metal hardware, and it runs Debian under the hood. Now the only VM I have running is GNS3. My last docker paperless ngx crashed so i wanted to try it wirh bare metal and it works. Linux is Linux essentially a lot of the fundamentals transfer but Debian distros have apt and Ubuntu also has snap for package management etc. For backups I use duplicacy. The other option is to wipe Proxmox, install TrueNAS bare metal and setup all my VMs inside TrueNAS, but I'm not entirely sold on that since some have mentioned inconsistencies with TrueNAS's VM system (might be outdated info), and I like the idea of having my VM host independent of my file server OS (might also be based on outdated info). Having used Debian for over 20 years, I still use Ubuntu on my laptop for simple "get things done" usability. I switched to proxmox and continued using zfs and have been very happy ever since. But you will likely still want to run some kind of OS as a NAS within proxmox and maybe another OS for your containers. Given limited resources here, I see no point in virtualizing anything, you're going to end up with two operating systems (plus virtualization overhead) just to run HA. IMO, TrueNAS is overkill for simple file sharing. My bare-metal NAS is simply minimal Debian 11 with the Cockpit web UI. 1 kernel). I use Debian on servers, because all the hardware is virtual, and I'm mostly doing custom stuff on top anyway. Even if you just have a single VM or LXC under Proxmox, I would still try it out. Proxmox doesn't support nested virtualization. Your RAM is rather low to be running Proxmox. install just debian on bare metal and put HA os with a virtual box (or something similar) and pass iGPU from there. According to the link provided "The client-only repository should be usable We would like to show you a description here but the site won’t allow us. So 3 12TB drives will give you 24 TB of usable storage. For a VM, or container, I would choose alpine. Yes it works with docker, but it works better (imo) in a VM or bare metal for that matter. Cockpit is an excellent web UI, but also stays out of the way. May 11, 2018 · I plan to install proxmox on a new machine. I'm debating between a bare metal Linux install of Ubuntu or something, vs proxmox and just firing up a VM in there. Proxmox is also much more mature as a hupervisor. For example, can't install Tailscale, on Proxmox host. I have been running Homeassistant on Proxmox for the past year or so without issue. And since I don't want to run frigate in a docker elsewhere, I went back from proxmox to HAOS bare metal. Not a huge deal. So there is different layers to be aware of. The only drawback is the community which isn't as big and great as the debian server community. Personally I'd prefer to install proxmox on top of a pure vanilla debian. It's more comparable to VMWare's vsphere than docker, i. I tried running TrueNAS scale bare metal and the virtualization and the docker app features just didn't come close to meeting my needs. Edit: It looks like it does support nested virtualization. Use proxmox and use the all the features. 6 with minimal variations. At far as all the k8s worker nodes ( bare metal or VM ) able to communicate with each other and with control plane in a way K8s requires, underline networking (VLAN or VPC) hardly matters. Plus I probably would have never tried LXC if it wasn't for Proxmox. It's been plenty stable for me, especially compared to freenas. Since I started using Frigate though I noted that the best install method is to use bare-metal where possible, which has set me looking at LXC containers. It uses Qemu/KVM, which essentially works like a type 1 hypervisor. Proxmox excels when you want the containers on a single physical host to be on different VLANs/subnets. So hp mini 15x17 sm is all i needed:). For a while, one of the nodes ran a NAS VM using an HBA and PCI passthrough; however, I recently added another Proxmox node and migrated the NAS to a bare-metal install. One thing I’ve seen people do (though I’d not recommend it) is to create a non-root user, and download a desktop environment on the proxmox server itself. The source code of Proxmox VE is licensed under the GNU AGPLv3 and free to download and use. When i tried this 2 years ago, i couldn't get it to work. The ESP32 series employs either a Tensilica Xtensa LX6, Xtensa LX7 or a RiscV processor, and both dual-core and single-core variations are available. I have tested in LXC containers as well but for less headaches I chose VMs. But it also has k3s to run containers. Having experimented with k8s for home usage for a long time now my favorite setup is to use proxmox on all hardware. With my new server I wasn’t sure if I wanted to go proxmox or Ubuntu. It's fine to use, most homelabs use only one machine and ZFS is built-in to proxmox. But Proxmox isn't much more than a nice admin layer over a Debian build anyways. I also run sorta headless Debian hosts with a kvm but only really interact with them via SSH over the network. I'd honestly go with bare metal TrueNAS SCALE. Newly installed Proxmox installation. 1) home assistant core 2) debian with docker for some containers i want to have separated from my main Rocky Linux server. x Kernel and also the upgraded 6. Only thing I had that caused a problem was using watchtower to manage other docker containers but that was easily replaced with other options that don’t cause my install to be unsupported. After Proxmox is up and running I put the server version of Debian 10, with no frills, just SSH. So I went the Alpine way! It's all simple and light so that's great. Proxmox doesn't get many CVEs, but that's not necessarily alone a basis to determine how secure a product is. At the bare metal level, you are usually using RHEL or Ubuntu, in which the kernel gets passed into the container. But i've spent 2 days now finding and following every guide and suggestion I could find. Nextcloud is an application "suite", you can run it on either of the former, or on bare metal, but it does not compare. To the host, the guest is just a set of files. You can always just switch it up if you have a good backup strategy. Usually you use Proxmox or any Hypervisor to run a pool of resources (multiple servers) and run multiple VMs for various use cases. Container escape is a thing, let's put the containers in a VM instead of bare metal OS (as root no less!) Some workloads are nice to "de-containerize". and I run HAOS, because it Just Works, and I can spend more time figuring out automation and other features, and less time managing the nuts and I was going to just build a regular bare metal windows PC but, since I've been spending a lot of time over the last month getting familiar with proxmox, I've seen a few videos recently on passing through the gpu to a windows VM and treating it as though it's a bare metal install while still getting all of the benefits of a proxmox host. So use the ISO installation instead of the OVF. I'm wondering about the pros and cons of Proxmox + Ubuntu vs bare metal Ubuntu for my use case. 5 mins boot time feels odd unless you're adding Proxmox boot time to it as well. As such, if you wanted to, you can install Proxmox components on top of vanilla Debian. Just use a CT and call it a day. You can think of it as cutting out the giant OS middleman. Any thoughts on the most efficient, cleanest, most reliable way to achieve my goals? Thanks all! However, proxmox has the regular Debian with bells and wistles and OOB web interface as ease off use multipliers for a homelabber. Now for the rant about TrueNas. docker VM with nvidia p400 and HBA passthrough with ZFS on same VM bare metal option. Three-node Proxmox VE cluster + bare-metal Proxmox Backup Server + bare-metal Hyper-V server + bare-metal DIY NAS (Debian-based). I personally prefer this solution for three reasons. Additionally, I understand that both Proxmox and Virt-Manager utilize KVM, so does it ultimately matter which approach I choose, or would running everything on bare metal be more suitable? Furthermore, if I choose to go with Proxmox, I'd like to allocate as much of my CPU and GPU resources as possible to my Windows, Fedora, and Kali instances. I am wondering if there is any big performance difference between running multiple websites with docker and npm comparing to running docker and npm in bare metal. And bare metal opnsense and bare metal truenas. Which of these would be eaiser and more reliable. Proxmox is great if you want to manage containers/VMs, handle backups, failover between proxmox hosts. ubuntu server with docker and ZFS bare metal + KVM I'm currently leaning towards the bare metal option since I have minimal need for VMs. Nothing wrong with either way, but personally I prefer the simplicity of proxmox and being able to run a VM, LXC and docker (in either of those) on the same host without much issues. Bare metal nginx used to be mostly just a reverse proxy for the other services. I tried both and figured that the lxc route would be the best and decided to bare metal install proxmox. Moved to Unriad bare metal and I am enjoying the experience, don't get me wrong spinning up vm's on Proxmox was so much easier and as others have mentioned it's certainly preferred as a dedicated Hypervisor but one thing that Unraid has over Proxmox is the very user friendly app store where you can spin up docker containers and the like with Unraid is kind of a do it all solution whereas proxmox is a hypervisor. maybe put jellyfin with docker or lxc and get easier hardware acceleration. 180. If you're going to use something like TrueNAS or other ZFS-type NAS software, then you're now going to be wanting to feed the VM lots of RAM so ARC can operate well. ESP32 is a series of low cost, low power system on a chip microcontrollers with integrated Wi-Fi and dual-mode Bluetooth. Thanks in advance :) But after all i have only 1 windows vm and 7-8 linux. Linux containers share the running kernel with the proxmox host, possibly resulting in a security issue. Now that I've sought, again, a simpler pre-packaged solution, I wonder if I should be worried about future development of AIO. vGPU is a Hyper-V and Proxmox territory these days for instance. Regardless, it shouldn't take 5 mins to boot Proxmox either I have HA in a VM on Proxmox on a completely different system I have Frigate running in a docker container. Theoretically kvm and proxmox have less overhead due to there being no emulation but I think most people won't see a major difference in real world conditions. Some of them have docker as the plugin or hypervisor as an additional thing, but they mostly focus on the storage side of things. My DIY, bare-metal, NAS is minimal Debian 11 with Docker Engine running 20 containers including Jellyfin and accompanying server apps. #2 is the reason I switched my OMV to bare metal. The containers are not persistent by default, so you'll need to mount some persistent storage to them for configurations, but then it's just a matter of backing up your configuration files and docker-compose files and you can run them anywhere. more "bare metal", less system overhead. So they can do much more than just running Plex with a few users. It will net the sum of 2 drive with the 3rd used as parity. Proxmox(on Debian), can run many Ubuntu (Computers/OS) with many containers (Docker). After debian, I first tried RancherOS which gave me some headaches because of kernel modules missing. The cpu overhead is <3% with kvm (assuming you didn’t get your cpu from an antique shop). Proxmox has tons of documentation, forums, and guides online to do just about anything. For storage, your host and guest can have different formats. curious if I can get the bare metal experience amd run proxmox like a workstation Technically not because one you throw a desktop environment on it then it's no longer a bare metals. e. APC Back-UPS RS 1500 monitored by NAS through USB. Preferences are fine, but the reality is that Proxmox offers ZFS support and is based on Debian, and also supports NFS/SAMBA shares. Proxmox = SysOps and K8s = DevOps. If you install HA OS on bare metal and plug a zigbee stick on it it gets automatically discovered. That's really not enough RAM to run both Proxmox and TrueNas unfortunately. I run a three-node, non-HA Proxmox cluster. But if I just install Debian on bare metal, than I install docker and Tailscale directly on the server. With proxmox as bare metal OS you have the advantage of running both VMs and LXC containers directly in it. If you ever upgrade your homelab server down the line you just need to backup them and restore it on a fresh install of proxmox and the VM will keep the same IP and it will be no different. Neither does Veeam free, but Macrium does - USB boot recovery environment works better than Veeam free, if you understand it's limits. With proxmox you can use the proxmox gui to manage all of your lxc containers and vms and then you can use portainer to easily manage your docker containers. They then add their own tooling, and web UI on top, and utilize other standard utilities like corosync, and ZFS. For one running bare metal, I would choose debian. Proxmox is built in top of Debian but many things are removed. Any time you have to shutdown/reboot your VM host it means OMV is down too, and that storage is unavailable. - boots in a VM like a dream and allows stupidly efficient and fast bare metal to VM restores - client doesn't care about Windows desktops vs servers. In Proxmox, I typically have two physical NICs available. boot the vm and do the storage vmotion while the vm was live. That's it. Jan 3, 2024 · Under the hood, Proxmox is Debian (PVE 8. Unraid is more a energy saving optimized NAS with a little bit docker and vm support. I have only used windows before. I'm running 2 proxmox nodes right now, the first one has pretty much every service I'm running (jellyfin, arr stack, home assistant, truenas, etc) and the other one is just running a single debian VM with pterodactyl on it. KVM and Proxmox are bare metal hypervisors (type 1) which allow arbitrary operating systems to run directly on hardware without any emulation. And i was wondering what would be the best option. Performance wise i'm not that happy and as I was not using any other VMs in the last months, i decided to move my VM to bare metal (overwriting the Proxmox installation). Vms all day. I'm in both camps. Better performance, no? Am I missing something? Edit: Man! It’s still running on “bare metal” and ends up being effectively the same in the end albeit without the Proxmox distro logos and boot screen etc. Proxmox LXC Intel Quick Sync Transcode for Plex - Spaaace [TUTORIAL] - Intel Coffeelake Plex hardware transcoding in Debian unprivileged LXC container | Proxmox Support Forum. However, everytime I try to passthrough the TPU to a VM it makes it unable to start (tried various distros, scripts, blacklisting). Also, here's an advantage of Proxmox over regular Debian: Proxmox's repositories provide newer versions of QEMU+KVM than the normal Debian repositories. I know docker is cool, but i don't want docker on my proxmox, otherweise i wouldn't have chosen proxmox. Currently using a Synology NAS but it’s not a great solution for transcoding video It’s a great solution for audio (plexamp) Why not HA OS on bare metal? Even if you do decide to have your own full OS, I would run HA in a Docker container instead of virtualizing another whole system. So i just installed on bare metal. In this case, testing on the Proxmox host system comparing to a Debian VM within (bookwork, 6. Build a NAS PC with a bare-metal OS and my various drives. But takes more resources. Install Ubuntu on server (linux os I'm most familiar with) and then install Postgres, or Proxmox, then Ubuntu VM with Postgres. Docker on LXC -> Oh Boy you will save lot of resources. Or you could install a desktop on Proxmox (from the Debian repos) if you prefer. Yep, I was in the same situation as yours. it also lets you learn more, as I am running Ubuntu and Debian systems just to learn the With a bare metal installation, this is never a worry has you have all of the components (files, configuration, database) separately and can always integrate those into a future implementation of NextCloud. Thanks. Typical docker + portainer + portainer agent installation on debian runs under 150 MB. So I would have to make a VM on top of Proxmox. But I agree that the performance of OMV on bare metal vs OMV in a VM on proxmox (even with virtual disks) is very close. Pass through the HD’s you want to use for Truenas + Apps (like Plex and all of the Arr’s) create zfs pools on pass through drives use 3 drives for each pool. On HA I use the Frigate Proxy and everything works great. After wasting so much time looking up KVM commands to administer VMs I tried Proxmox. This machine currently just has windows on it. UnRAID, TrueNAS, OMV - NAS solutions that could run inside hypervisor as the VMs or bare-metal on hardware. Proxmox on the bare metal; VM for Home Assistant (use the proxmox script to set it up - super simple; easy find using google “proxmox home assistant install script”) Separate VM for ZoneMinder Third VM for all my other docker containers. It's still under the recommended specs for TrueNAS but I don't think you'll have any real issues with that. Install Proxmox and don't look back . I fell in love with how easy that stupid web UI made things. The answer if yes. A place to share, discuss, discover, assist with, gain assistance for, and critique self-hosted alternatives to our favorite web apps, web services, and online tools. Edit: typos Personally, I have 30+ years IT experience, work with virtualization every day, both bare metal hypervisor and docker containers, VMware products from Workstation to ESX, Xen, ProxMox, KVM/QEMU/LXC. Whatever might be the "best" option is entirely up to you. You can also do the other way around with TrueNAS bare metal and VMs for the rest since TrueNAS supports VMs. x = Debian 12/Bookworm). Run a kubernetes cluster can be more cost effective on a Hypervisor than on bare metal. Separate server for all media using nfs exports for plex server. Bare metal nginx is still there as a file serving web server. I have Proxmox in mine and I run Plex on an LXC (container) and I have Portainer in another LXC running a bunch of Docker services. Proxmox - hypervisor, which is primarily focusing on the VMs and containers. I'm a Hyper-V guy myself, but Proxmox or any Type 1 hypervisor will do the trick. If you are not 100% sure about what your final configuration will be, Proxmox allows for the flexibility of trying different NAS management OS without having to go through a bare metal reinstallation every time. There will be a little added complexity in setting it up because you will need to pass through the drives that you will use to the VM. Templates and clones make it super easy to rebuild stuff if needed. So im good. I tried it once and then I have to reinstall Proxmox CE. The difference in performance in bare metal vs virtualization on any moderately modern cpu will be negligible comparing to a fluctuation in your ISP network. Install proxmox on bare server and run HASSOS and pihole container Install Ubuntu + kubernetes and run HASS and pihole containers. I bought a cheap intel NUC and installed proxmox on that for HomeAssistant and tinkering about with other things that need their own VM. USB pass through generally works good for simple devices like a zigbee dongle or usb Bluetooth-stick. It has advantages. That's why i got the extra strep over the lxc. I’ll occasionally go to a docker or even truenas for secondary Plex servers (guest access, testing, etc) but my primary has typically been bare metal. I'm sorry for asking as there are so many of this same question. should probably test this. I installed Proxmox Backup Client on my NAS and use PBS for backups. That only leaves you with 2 GB to play around with, which is basically just one very light VM. First with home assistant in a vm then proxmox in HA vm and then as a Frigate container on proxmox. Proxmox is a Linux distribution. But that's semantics at this point. It hinders with proxmox. I've done it for nothing more than wanting to be able to encrypt the entire installation (which the Proxmox ISO does not give you the option for, but Debian does). 40 Mbit/s Down and only 10 Mbit/s up on the Proxmox vs 452. "Windows is Jan 22, 2022 · The KVM plugin is not as advanced as Proxmox but it is much simpler. It can see the smart data, etc for for the six drives attached to the card. And here and there I spin a new VM for testing things. For work, Its RHEL all the way. Not really. If you only have a single system, your best option might be Proxmox to host the guest HAOS in a VM, but at the host OS set up the docker container for Frigate. Doing a bit of benchmarking vs bare metal. I have a bit of everything. I haven't used proxmox before but did set up quite a few debian machines already and feel very comfortable with it. Ok load Proxmox onto bare metal. 2. I've not worked with proxmox before and it looked a bit tricky. If you are considering K8s or K3s on bare-metal, then you also could consider using Ansible. Oct 15, 2022 · I've been playing around with Proxmox for over a year now, having one main VM running 24/7 with my main application in docker (like Paperless, Plex, HA etc). Sep 6, 2023 · If I use Proxmox it's kind of simple to do this with Keepalived, because everything will use internal IP's and it's fine. A little higher than the Windows VM (1400), but not exactly surprising - it's possible that the Linux VM outperforming the Windows VM (1600 vs 1400) and the Proxmox baremetal outperforming the Windows baremetal (2000 vs 1700) have a common cause unrelated to our main predicament (i. Yes people will say its easy but damn if I wasn't frustrated remembering the lines I had to copy and paste into Portainer to pull the update and then to edit the ports to suit my configs. Yeah if you have no interest in running other services then Ubuntu bare metal, probably using docker, is going to be simpler. I'd then run Arch Linux on bare metal as my main OS, using ZFS as the root filesystem, and passing through the 2080 Ti to Windows for games, and looking glass for the monitor, or using nvidia-xrun when gaming on Linux. If it's strictly a NAS I'd just install TrueNAS on the bare metal. A virtual machine completely isolates the machine from the proxmox kernel. docker VM with nvidia p400 passthrough and ZFS on TrueNAS VM (allows CIFS mounts to work) proxmox option 3. With the bare-metal installation, you'll get a complete operating system based on Debian GNU/Linux, 64-bit, a Proxmox VE kernel with KVM and container support, great tools for backup/restore and HA clustering, and much more We would like to show you a description here but the site won’t allow us. Most modern IT uses containers for applications so the distro doesn't matter that much. I, for instance, prefer to run home assistant OS in a VM instead of in docker. The question is what should be on docker vs virtual machine vs bare metal For me; Bare Metal: Storage Server Home Automation (4 RS232, 2 RS485, USB Z-wave, dedicated net interface for many network applications) VM Server (xcp-ng) VM's: Docker Server Other stuff I want a windows or a dedicated network interface May 8, 2024 · I think my initial plan was actually number 2: PVE is runing bare metal and on that I run the desktop manager. Works great going on 3 years. Dec 12, 2024 · I have an ASMedia 1166 based adapter that I pass through to TrueNAS and TrueNAS behaves as if it is operating on bare metal. Single master k3s with many nodes, one vm per physical machine. The 2 main cons I see are: Get the Reddit app Scan this QR code to download the app now If you are stuck to run Linux containers best be would be to run Proxmox bare metal and a TrueNas VM You run Proxmox/openstack on the hardware (usually several bare metal machines) and it gives you the tools to manage them as a "pool" of resources. Remote access to console and a GUI. At A certain point I just said fk it and went bare Or maybe the app isn’t supported on the OS I choose (Debian 11). In my use case I prefer to keep my virtual machines as far apart from the bare metal boat as possible. Any knowledge and experience people can share about what would be the best solution would be much appreciated. Up until now I've always just used PCIe passthrough but this is impacted inference speeds which averages at Proxmox will teach you about Debian as well as virtualization. Hi there fellow Home-Assistanters! I'm currently in the process of switching from a Raspberry Pi 3+ to a small Workstation PC (Core i5, 8GB RAM, SSD). On the proxmox, I only have 2 running vm's. I recently added MetalLB to Kubernetes and set up ingress-nginx as an ingress controller. Under the hood proxmox and unraid use the same technology, so performance should be same. My inclination would be a hypervisor for any bare metal instance. if vmware could write a simple flat vmdk file on that nas, one could in theory mv that flat. I moved to bare metal because dealing with updates to container got too irritating for my old feeble mind. Proxmox is more powerful when it comes to more advanced vm features, like snapshots, clustering, etc. I really enjoy Proxmox and it served me really well in the past 3 years. Also, my linux skills were pretty green, so i was a bit apprehensive of trying to "get it to work. I run two machines in my homelab along with handful of raspberry pi. I also run a pihole lxc on proxmox which is backup for pihole running on one of the pi. I don't need big gun for Proxmox im tired from servers. Similarly, restoring those backups onto other Proxmox hosts is super easy if all hosts mount the same NFS storage. The containerization approach is already keeping the host OS clean, and you can manage everything from the proxmox interface. I intend to have a primary SSD for the OS and I want to mirror 2 12TB drives initially, with other random drives plugged in as separate storage for backups (I'm just trying to make use of old drives where I can they still work great, but are smaller sizes and various sizes). The reason for passthrough is that you realllllllllyyy should be using a coral accelerator to lighten the load on the CPU. 52 Mbit/s Down and 395 Mbit/s up on the baremetal Looks like I have some configuration on the network to take care of. Especially when you start using HA and clustering a Hypervisor may be more suitable. Jan 21, 2024 · OK, so we're getting in the region of 1500-1600 single-thread passmark points in a Linux VM. 1. Nov 4, 2024 · I also grappled with this one for sometime. Oct 16, 2014 · The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway. Yes, you can do the same with bare metal Linux, but I like the separation Proxmox provides. So i dont need Proxmox for linux vms . I actually started this journey last year and have attempted to setup Frigate multiple times. The simple answer: yes, you can install Proxmox on top of Debian. ) on bare-metal. As others have said, do both: Install docker in a VM on Proxmox. One good option (for me) is keeping NVMe drives under Proxmox and pass through the SATA controller to the NAS OS. We think our community is one of the best thanks to people like you! The subreddit for all things related to Modded Minecraft for Minecraft Java Edition --- This subreddit was originally created for discussion around the FTB launcher and its modpacks but has since grown to encompass all aspects of modding the Java edition of Minecraft. forget about proxmox. It's Debian but that matters not for virtualization. I have a proxmox machine with some vm's on it. apcupsd service installed on all systems - configured as master on NAS and as network client on other systems. (good thing, I'll play my movies etc. Then there are apps that have better documentation for bare metal or directly mention my OS as supported. Just do whatever seems fun to you. Because i have 3 Proxmox CTs an 5 docker conts including plex etc. I’ve gone for option 2; and it has been serving me well for a couple of years now. Proxmox uses Debian stable with KVM (Linux built in virtualization) and qemu. Being a VMware admin by trade, I can say most of things it is missing are not typically needed (like clustering). Both options are good. Running plex on bare metal. Bare metal is cool but unless you need something specific like direct hardware access for high performance computing use vms all day This is pretty much literally the point of containers. 2. It's more down to personal preference than being a home vs. A rocky linux machine with mostly docker containers. Running Docker, and later K8s or K3s, on Debian or Ubuntu bare-metal servers may suit your purposes better than running it on top of PVE. I’ve been a Plex pass user on bare metal for over 10 years. I've been trying things out with my dual edge TPU in Proxmox 8 and so far I've managed to set Frigate in LXC (using tteck's script or manually creating my own Docker system on a Debian LXC). Kubernetes creates its own overylay network for pods networking on top of an underlay network which will be a VLAN in case of bare metal servers and VPC for VMs. TrueNas I had to dig through 8 forum posts to figure out APT was disabled when I tried to install PBS. I'm running quite a few Addons and some complex Automations in Node-Red. Debian is a great base to build on, but it's not a great out of the box end-user experience. But if I use debian it will be the public ip's, and the hosting I'm using ( OVH ), has something that allows this called Floating IP's, but it takes around 5 minutes to do the switch, so it's 5 minutes that the site is down. It is now the web frontend for all the web services, including Nexus and nginx. ykbhhlqqqyuzlazggtknesedujbcgnmcsfjnngehkeoqblzprooya