Curious to know what the experiences are for those who are sticking to bare metal. Would like to better understand what keeps such admins from migrating to containers, Docker, Podman, Virtual Machines, etc. What keeps you on bare metal in 2025?

  • yessikg
    link
    fedilink
    06 months ago

    It’s so simple that it takes so much less time, one day I may move to Podman but I need to have the time to learn. I host Jellyfin

  • @erock@lemmy.ml
    link
    fedilink
    English
    06 months ago

    Here’s my homelab journey: https://bower.sh/homelab

    Basically, containers and GPU is annoying to deal with, GPU pass through to a VM is even more annoying. Most modern hobbyist GPUs also do not support splitting your GPU. At the end of the day, it’s a bunch of tinkering which is valuable if that’s your goal. I learned what I wanted, now I’m back to arch running everything with systemd and quadlet

  • @HiTekRedNek@lemmy.world
    link
    fedilink
    English
    06 months ago

    In my own experience, certain things should always be on their own dedicated machines.

    My primary router/firewall is on bare metal for this very reason.

    I do not want to worry about my home network being completely unusable by the rest of my family because I decided to tweak something on the server.

    I could quite easily run OpnSense in a VM, and I do that, too. I run proxmox, and have OpnSense installed and configured to at least provide connectivity for most devices. (Long story short: I have several subnets in my home network, but my VM OpnSense setup does not, as I only had one extra interface on that equipment, so only devices on the primary network would work)

    And tbh, that only exists because I did have a router die, and installed OpnSense into my proxmox server temporarily while awaiting new-to-me equipment.

    I didn’t see a point in removing it. So it’s there, just not automatically started.

    • @AA5B@lemmy.world
      link
      fedilink
      English
      0
      edit-2
      6 months ago

      Same here. In particular I like small cheap hardware to act as appliances, and have several raspberry pi.

      My example is home assistant. Deploying on its own hardware means an officially supported management layer, which makes my life easier. It is actually running containers but i don’t have to deal with that. It also needs to be always available so i use efficient “right sized” hardware and it works regardless whether im futzing with my “lab”

      • @Damage@feddit.it
        link
        fedilink
        English
        06 months ago

        My example is home assistant. Deploying on its own hardware means an officially supported management layer, which makes my life easier.

        If you’re talking about backups and updates for addons and core, that works on VMs as well.

        • @AA5B@lemmy.world
          link
          fedilink
          English
          06 months ago

          For my use case, I’m continually fiddling with my VM config. That’s my playground, not just the services hosted there. I want home assistant to always be available so it can’t be there.

          I suppose I could have a “production “ vm server that I keep stable, separately from my “dev” vm server but that would be more effort. Maybe it’s simply that I don’t have many services I want to treat as production, so the physical hardware is the cheapest and easiest option

  • @splendoruranium@infosec.pub
    link
    fedilink
    English
    06 months ago

    Curious to know what the experiences are for those who are sticking to bare metal. Would like to better understand what keeps such admins from migrating to containers, Docker, Podman, Virtual Machines, etc. What keeps you on bare metal in 2025?

    If it aint broke, don’t fix it 🤷

  • Magiilaro
    link
    fedilink
    English
    06 months ago

    My servers and NAS were created long before Docker was a thing, and as I am running them on a rolling release distribution there never was a reason to change anything. It works perfectly fine the way it is, and it will most likely run perfectly fine the next 10+ years too.

    Well I am planning, when I find the time to research a good successor, to replace my aging HPE ProLiant MicroServer Gen8 that I use as Homeserver/NAS. Maybe I will then setup everything clean and migrate the services to docker/podman/whatever is fancy then. But most likely I will only transfer all the disks and keep the old system running on newer hardware. Life is short…

  • @ZiemekZ@lemmy.world
    link
    fedilink
    English
    06 months ago

    I consider them unnecessary layers of abstraction. Why do I need to fiddle with Docker Compose to install Immich, Vaultwarden etc.? Wouldn’t it be simpler if I could just run sudo apt install immich vaultwarden, just like I can do sudo apt install qbittorrent-nox today? I don’t think there’s anything that prohibits them from running on the same bare metal, actually I think they’d both run as well as in Docker (if not better because of lack of overhead)!

    • @boonhet@sopuli.xyz
      link
      fedilink
      English
      06 months ago

      Both your examples actually include their own bloat to accomplish the same thing that Docker would. They both bundle the libraries they depend on as part of the build

  • @Evotech@lemmy.world
    link
    fedilink
    English
    06 months ago

    It’s just another system to maintain, another link in the chain that can fail.

    I run all my services on my personal gaming pc.

  • @medem@lemmy.wtf
    link
    fedilink
    English
    06 months ago

    The fact that I bought all my machines used (and mostly on sale), and that not one of them is general purpose, id est, I bought each piece of hardware with a (more or less) concrete idea of what would be its use case. For example, my machine acting as a file server is way bigger and faster than my desktop, and I have a 20-year-old machine with very modest specs whose only purpose is being a dumb client for all the bigger servers. I develop programs in one machine and surf the internet and watch videos on the other. I have no use case for VMs besides the Logical Domains I setup in one of my SPARC hosts.

  • @neidu3@sh.itjust.works
    link
    fedilink
    English
    06 months ago

    I started hosting stuff before containers were common, so I got used to doing it the old fashioned way and making sure everything played nice with each other.

    Beyond that, it’s mostly that I’m not very used to containers.

  • sj_zero
    link
    fedilink
    06 months ago

    I’m using proxmox now with lots of lxc containers. Prior to that, I used bare metal.

    VMs were never really an option for me because the overhead is too high for the low power machines I use – my entire empire of dirt doesn’t have any fans, it’s all fanless PCs. More reliable, less noise, less energy, but less power to throw at things.

    Stuff like docker I didn’t like because it never really felt like I was in control of my own system. I was downloading a thing someone else made and it really wasn’t intended for tinkering or anything. You aren’t supposed to build from source in docker as far as I can tell.

    The nice thing about proxmox’s lxc implementation is I can hop in and change things or fix things as I desire. It’s all very intuitive, and I can still separate things out and run them where I want to, and not have to worry about keeping 15 different services running on the same version of whatever common services are required.

    • @boonhet@sopuli.xyz
      link
      fedilink
      English
      06 months ago

      Actually docker is excellent for building from source. Some projects only come with instructions for building in Docker because it’s easier to make sure you have tested versions of tools.

  • @7rokhym@lemmy.ca
    link
    fedilink
    English
    06 months ago

    Not knowing about Incus (LXD). It’s a life changer. Would never run any service on bare metal again.

    Using GenAI to develop my Terraform and Ansible playbooks is magical. Also, use it to document everything in beautiful HTML docs from the outputs. Amazing.

  • billwashere
    link
    fedilink
    English
    0
    edit-2
    6 months ago

    Ok I’m arguing for containers/VMs and granted I do this for a living… I’m a systems architect so I build VMs and containers pretty much all the time time at work… but having just one sorta beefy box at home that I can run lots of different things is the way to go. Plus I like to tinker with things so when I screw something up, I can get back to a known state so much easier.

    Just having all these things sandboxed makes it SO much easier.

  • @sem@lemmy.blahaj.zone
    link
    fedilink
    English
    06 months ago

    For me the learning curve of learning containers does not match the value proposition of what benefits they’re supposed to provide.

    • billwashere
      link
      fedilink
      English
      06 months ago

      I really thought the same thing. But it truly is super easy. At least just the containers like docker. Not kubernetes, that shit is hard to wrap your head around.

      Plus if you screw up one service and mess everything up, you don’t have to rebuild your whole machine.

  • Billegh
    link
    fedilink
    English
    06 months ago

    It depends on the service and the desired level of it stack.

    I generally will run services directly on things like a raspberry pi because VMs and containers offer added complexity that isn’t really suitable for the task.

    At work, I run services in docker in VMs because the benefits far outweigh the complexity.

  • @OnfireNFS@lemmy.world
    link
    fedilink
    English
    06 months ago

    This reminds me of a question I saw a couple years ago. It was basically why would you stick with bare metal over running Proxmox with a single VM.

    It kinda stuck with me and since then I’ve reimaged some of my bare metal servers with exactly that. It just makes backup and restore/snapshots so much easier. It’s also really convenient to have a web interface to manage the computer

    Probably doesn’t work for everyone but it works for me