Those who are hosting on bare metal: What is stopping you from using Containers or VM's? What are you self hosting?

Comments

• atzanteol@sh.itjust.works ⁨3⁩ ⁨weeks⁩ ago

  Containers run on “bare metal” in exactly the same way other processes on your system do. You can even see them in your process list FFS. They’re just running in different cgroup’s that limit access to resources.

  Yes, I’ll die on this hill.

  source

  • sylver_dragon@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

    But, but, docker, kubernetes, hyper-scale convergence and other buzzwords from the 2010’s! These fancy words can’t just mean resource and namespace isolation!

    In all seriousness, the isolation provided by containers is significant enough that administration of containers is different from running everything in the same OS. That’s different in a good way though, I don’t miss the bad old days of everything on a single server in the same space. Anyone else remember the joys of Windows Small Business Server? Let’s run Active Directory, Exchange and MSSQL on the same box. No way that will lead to prob… oh shit, the RAM is on fire.

    source

    • sugar_in_your_tea@sh.itjust.works ⁨3⁩ ⁨weeks⁩ ago

      kubernetes

      Kubernetes isn’t just resource isolation, it encourages splitting services across hardware in a cluster. So you’ll get more latency than VMs, but you get to scale the hardware much more easily.

      Those terms do mean something, but they’re a lot simpler than execs claim they are.

      source

      • -> View More Comments
    • AtariDump@lemmy.world ⁨2⁩ ⁨weeks⁩ ago

      …oh shit, the RAM is on fire.

      We don’t need no water let the mothefuxker burn.

      Burn mothercucker, burn.

      (Thanks phone for the spelling mistakes that I’m leaving).

      source
    • atzanteol@sh.itjust.works ⁨3⁩ ⁨weeks⁩ ago

      Oh for sure - containers are fantastic. Even if you’re just using them as glorified chroot jails they provide a ton of benefit.

      source
  • Semi_Hemi_Demigod@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

    Learning this fact is what got me to finally dockerize my setup

    source
  • arcayne@lemmy.today ⁨3⁩ ⁨weeks⁩ ago

    Move over, bud. That’s my hill to die on, too.

    source
  • FailBetter@crust.piefed.social ⁨3⁩ ⁨weeks⁩ ago

    Speak english doctor! But really is this a fancy way of saying its ok to docker all the things?

    source
• sepi@piefed.social ⁨3⁩ ⁨weeks⁩ ago

  “What is stopping you from” <- this is a loaded question.

  We’ve been hosting stuff long before docker existed. Docker isn’t necessary. It is helpful sometimes, and even useful in some cases, but it is not a requirement.

  I had no problems with dependencies, config, etc because I am familiar with just running stuff on servers across multiple OSs. I am used to the workflow. I am also used to docker and k8s, mind you - I’ve even worked at a company that made k8s controllers + operators, etc. I believe in the right tool for the right job, where “right” varies on a case-by-case basis.

  tl;dr docker is not an absolute necessity and your phrasing makes it seem like it’s the only way of self‐hosting you are comfy with. People are and have been comfy with a ton of other things for a long time.

  source

  • kiol@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

    Question is totally on purpose, so that you’ll fill in what it means to you. The intention is to get responses from people who are not using containers, that is all. Thank you for responding!

    source

    • lka1988@lemmy.dbzer0.com ⁨2⁩ ⁨weeks⁩ ago

      Honest response - respect.

      source
    • sepi@piefed.social ⁨2⁩ ⁨weeks⁩ ago

      What is stopping you from running HP-UX for all your workloads? The questuon is totally in purpose so that you’ll fill in what it means to you.

      source
• nucleative@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

  I’ve been self-hosting since the '90s. I used to have an NT 3.51 server in my house. I had a dial in BBS that worked because of an extensive collection of .bat files that would echo AT commands to my COM ports to reset the modems between calls. I remember when we had to compile the slackware kernel from source to get peripherals to work.

  But in this last year I took the time to seriously learn docker/podman, and now I’m never going back to running stuff directly on the host OS.

  I love it because I can deploy instantly… Oftentimes in a single command line. Docker compose allows for quickly nuking and rebuilding, oftentimes saving your entire config to one or two files.

  And if you need to slap in a traefik, or a postgres, or some other service into your group of containers, now it can be done in seconds completely abstracted from any kind of local dependencies. Even more useful, if you need to move them from one VPS to another, or upgrade/downgrade core hardware, it’s now a process that takes minutes. Absolutely beautiful.

  source

  • roofuskit@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

    Hey, you made my post for me though I’ve been using docker for a few years now. Never, looking, back.

    source
• fubarx@lemmy.world ⁨2⁩ ⁨weeks⁩ ago

  Have done it both ways. Will never go back to bare metal. Dependency hell forced multiple clean installs down to bootloader.

  The only constant is change.

  source
• zod000@lemmy.dbzer0.com ⁨2⁩ ⁨weeks⁩ ago

  Why would I want add overheard and complexity to my system when I don’t need to? I can totally see legitimate use bases for docker, and work for purposes I use VMs constantly. I just don’t see a benefit to doing so at home.

  source

  • boonhet@sopuli.xyz ⁨2⁩ ⁨weeks⁩ ago

    Main benefit of Docker for home is Docker compose IMO. Makes it so easy to reuse your configuration

    source

    • cichy1173@szmer.info ⁨2⁩ ⁨weeks⁩ ago

      Then check IaC, for example with Terraform or Ansible

      source

      • -> View More Comments
• enumerator4829@sh.itjust.works ⁨3⁩ ⁨weeks⁩ ago

  My NAS will stay on bare metal forever. Any complications there is something I really don’t want. Passthrough of drives/PCIe-devices works fine for most things, but I won’t use it for ZFS.

  As for services, I really hate using Docker images with a burning passion. I’m not trusting anyone else to make sure the container images are secure - I want the security updates directly from my distribution’s repositories, and I want them fully automated, and I want that inside any containers. Having Nixos build and launch containers with systemd-nspawn solves some of it. The actual docker daemon isn’t getting anywhere near my systems, but I do have one or two OCI images running. Will probably migrate to small VMs per-service once I get new hardware up and running.

  Additionally, I never found a source of container images I feel like I can trust long term. When I grab a package from Debian or RHEL, I know that package will keep working without any major changes to functionality or config until I upgrade to the next major. A container? How long will it get updates? How frequently? Will the config format or environment variables or mount points change? Will a threat actor assume control of the image? (Oh look, all the distros actually enforce GPG signatures in their repos!)

  So, what keeps me on bare metal? Keeping my ZFS pools safe. And then just keeping away from the OCI ecosystem in general, the grass is far greener inside the normal package repositories.

  source

  • towerful@programming.dev ⁨3⁩ ⁨weeks⁩ ago

    A NAS as bare metal makes sense.
    It can then correctly interact with the raw disks.

    You could pass an entire HBA card through to a VM, but I feel like it should be horses for courses.
    Let a storage device be a storage device, and let a hypervisor be a hypervisor.

    source
  • zod000@lemmy.dbzer0.com ⁨2⁩ ⁨weeks⁩ ago

    I feel like this too. I do not feel comfortable using docker containers that I didn’t make myself. And for many people, that defeats the purpose.

    source
• mesamunefire@piefed.social ⁨3⁩ ⁨weeks⁩ ago

  Al my services run on bare metal because its easy. And the backups work. It heavily simplifies the work and I dont have to worry about things like a virtual router, using more cpu just to keep the container…contained and running. Plus a VERY tiny system can run:

  1. Peertube
  2. GoToSocial + client
  3. RSS
  4. search engine
  5. A number of custom sites
  6. backups
  7. Matrix server/client
  8. and a whole lot more

  Without a single docker container. Its using around 10-20% of the RAM and doing a dd once in a while keeps everything as is. Its been 4 years-ish and has been working great. I used to over-complicate everything with docker + docker compose but I would have to keep up with the underlining changes ALL THE TIME. It sucked, and its not something I care about on my weekends.

  I use docker, kub, etc…etc… all at work. And its great when you have the resources + coworkers that keep things up to date. But I just want to relax when I get home. And its not the end of the world if any of them go down.

  source

  • Auli@lemmy.ca ⁨3⁩ ⁨weeks⁩ ago

    Oh so the other 80% of your RAM can sit there and do nothing? My RAM is always around 80% or so as its caching stuff like it’s supposed to.

    source

    • mesamunefire@piefed.social ⁨3⁩ ⁨weeks⁩ ago

      Hahaha that’s funny. I hope your not serous.

      source

      • -> View More Comments
  • Miaou@jlai.lu ⁨2⁩ ⁨weeks⁩ ago

    Assuming you run Synapse, that uses more than 1.5GB RAM just idling, your system has at the very least 16GB of RAM… Hardly what I’d call “very tiny”

    source

    • mesamunefire@piefed.social ⁨2⁩ ⁨weeks⁩ ago

      …ok so Im lying about my system for…some reason?

      Synapse looks like its using 200M right now. It jumps to 1 GB when being heavily used, but I only use it for piefed and a couple of other local rooms. Honestly its not doing so much for us so we were thinking of getting rid of it. Its irritating to keep having to set up new devices and no one is really using it.

      Peertube is much bigger running around 500MB just doing its thing.

      Its a single family instance…you ok?

      ```

      source
  • WhyJiffie@sh.itjust.works ⁨3⁩ ⁨weeks⁩ ago

    what do you run for RSS?

    also, I hope you are not doing backups by dding an in use filesystem

    source

    • mesamunefire@piefed.social ⁨3⁩ ⁨weeks⁩ ago

      Freshrss. Sips resources.

      The dd I do when I want. I have a script I tested a while back. The machine won’t be on yeah. Its just a small image with the software.

      source
  • kiol@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

    Do you use any tools for management, such as Ansible or similar?

    source

    • mesamunefire@piefed.social ⁨3⁩ ⁨weeks⁩ ago

      Couple of custom bash scripts for the backups. Ive used amsible at work. Its awesome, but my own stuff doesn’t require any robustness.

      source
• laserjet@lemmy.dbzer0.com ⁨3⁩ ⁨weeks⁩ ago

  Every time I have tried it just introduces a layer of complexity I can’t tolerate. I have struggled to learn everything required to run a simple Debian server. I don’t care what anyone says, docker is not simpler or easier. Maybe it is when everything runs perfectly but they never do so you have to consider the eventual difficulty of troubleshooting. And that would be made all the more cumbersome if I do not yet understand the fundamentals of Linux system.

  However I do keep a list of packages I want to use that are docker-only. So if one day I feel up to it I’ll be ready to go.

  source

  • kiol@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

    Did you try compose scripts as opposed to docker run

    source

    • laserjet@lemmy.dbzer0.com ⁨3⁩ ⁨weeks⁩ ago

      I don’t know. both? probably? I tried a couple of things here and there. it was plain that bringing in docker would add a layer of obfuscation to my system that I am not equipped to deal with. So I rinsed it from my mind.

      If you think it’s likely that I followed some “how to get started with docker” tutorial that had completely wrong information in it, that just demonstrates the point I am making.

      source
• missfrizzle@discuss.tchncs.de ⁨2⁩ ⁨weeks⁩ ago

  pff, you call using an operating system bare metal? I run my apps as unikernels on a grid of Elbrus chips I bought off a dockworker in Kamchatka.

  and even that’s overkill. I prefer synthesizing my web apps into VHDL and running them directly on FPGAs.

  until my ASIC shuttle arrives from Taipei, naturally, then I bond them directly onto Ethernet sockets.

  /uj not really but that’d be sick as hell.

  source

  • Tangent5280@lemmy.world ⁨2⁩ ⁨weeks⁩ ago

    I just imagine what the output of any program would be. Follow me, set yourself free!

    source
• 30p87@feddit.org ⁨3⁩ ⁨weeks⁩ ago

  That I’ve yet to see a containerization engine that actually makes things easier, especially once a service does fail or needs any amount of customization. I’ve two main services in docker, piped and webodm, both because I don’t have the time (read: am too lazy) to write a PKGBUILD. Yet, docker steals more time than maintaining a PKGBUILD, with random crashes (undebuggable, as the docker command just hangs when I try to start one specific container), containers don’t start properly after being updated/restarted by watchtower, and debugging any problem with piped is a chore, as logging in docker is the most random thing imagineable. With systemd, it’s in journalctl, or in /var/log if explicitly specified or obviously useful (eg. in multi-host nginx setups). With docker, it could be a logfile on the host, on the guest, or stdout. Or nothing, because, why log after all, when everything “just works”? (Yes, that’s a problem created by container maintainers, but one you can’t escape using docker. Or rather, in the time you have, you could more easily properly(!) install it bare metal) Also, if you want to use unix sockets to more closely manage permissions and prevent roleplaying a DHCP and DNS server for ports (by remembering which ports are used by which of the 25 or so services), you’ll either need to customize the container, or just use/write a PKGBUILD or similar for bare metal stuff.

  Also, I need to host a python2.7 django 2.x or so webapp (yes, I’m rewriting it), which I do in a Debian 13 VM with Debian 9 and Debian 9 LTS repos, as it most closely resembles the original environment, and is the largest security risk in my setups, while being a public website. So into qemu it goes.

  And, as I mentioned, either stuff is officially packaged by Arch, is in the AUR or I put it into the AUR.

  source

  • deadcade@lemmy.deadca.de ⁨3⁩ ⁨weeks⁩ ago

    Personally I have seen the opposite from many services. Take Jitsi Meet for example. Without containers, it’s like 4 different services, with logs and configurations all over the system. It is a pain to get running, as none of the services work without everything else being up. In containers, Jitsi Meet is managed in one place, and one place only. (When using docker compose,) all logs are available with docker compose logs, and all config is contained in one directory.

    It is more a case-by-case thing whether an application is easier to set up and maintain with or without docker.

    source

    • Jakeroxs@sh.itjust.works ⁨2⁩ ⁨weeks⁩ ago

      For logs dozzle is also fantastic, and you can do “agents” if you have multiple docker nodes and connect them togetherb

      source
  • renegadespork@lemmy.jelliefrontier.net ⁨3⁩ ⁨weeks⁩ ago

    Do you host on more than one machine? Containerization / virtualization begins to shine most brightly when you need to scale / migrate across multiple servers. If you’re only running one server, I definitely see how bare metal is more straight-forward.

    source

    • zod000@lemmy.dbzer0.com ⁨2⁩ ⁨weeks⁩ ago

      This is a big part of why I don’t use VMs or containers at home. All of those abstractions only start showing their worth once you scale them out.

      source

      • -> View More Comments
    • 30p87@feddit.org ⁨3⁩ ⁨weeks⁩ ago

      One main server, with backup servers being very easy to get up and running, either by full-restoring the backup, or installing and restoring specific services. As everything’s backed up to a Hetzner Storage Box, I can always restore it (if I have my USB sticks with the keyfiles).

      I don’t really see the need for multiple running hosts, apart from:

      • Router
      • Workstation which has a 1070 in it, if I need a GPU for something. My 1U server only has space for a low profile and one slot GPU/HPC processor, and one of those would cost way more than its value over my old 1070 would be.

      source
  • towerful@programming.dev ⁨3⁩ ⁨weeks⁩ ago

    especially once a service does fail or needs any amount of customization.

    A failed service gets killed and restarted. It should then work correctly.
    If it fails to recover after being killed, then it’s not a service that’s fully ready for containerisation.
    So, either build your recovery process to account for this… or fix it so it can recover.
    It’s often why databases are run separately from the service. Databases can recover from this, and the services are stateless - doesn’t matter how many you run or restart.

    As for customisation, if it isn’t exposed via env vars then it can’t be altered.
    If you need something beyond the env vars, then you use that container as a starting point and make your customisation a part of your container build processes via a dockerfile (or equivalent)

    It’s a bit like saying “chisels are great. But as soon as you need to cut a fillet steak, you need to sharpen a side of the chisel instead of the tip of the chisel”.
    It’s using a chisel incorrectly.

    source

    • 30p87@feddit.org ⁨3⁩ ⁨weeks⁩ ago

      Exactly. Therefore, docker is not useful for those purposes to me, as using arch packages (or similar) is easier to fulfill my needs.

      source
  • Semi_Hemi_Demigod@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

    You can customize and debug pretty easily, I’ve found. You can create your own Dockerfile based on one you’re using and add customizations there, and exec will get you into the container.

    source
• splendoruranium@infosec.pub ⁨2⁩ ⁨weeks⁩ 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 🤷

  source
• ZiemekZ@lemmy.world ⁨2⁩ ⁨weeks⁩ 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)!

  source

  • boonhet@sopuli.xyz ⁨2⁩ ⁨weeks⁩ 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

    source

    • Mubelotix@jlai.lu ⁨2⁩ ⁨weeks⁩ ago

      It’s not just libraries in a docker

      source

      • -> View More Comments
    • communism@lemmy.ml ⁨2⁩ ⁨weeks⁩ ago

      Idk about Immich but Vaultwarden is just a Cargo project no? Cargo statically links crates by default but I think can be configured to do dynamic linking too. The Rust ecosystem seems to favour static linking in general just by convention.

      source

      • -> View More Comments
• sem@lemmy.blahaj.zone ⁨2⁩ ⁨weeks⁩ ago

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

  source

  • billwashere@lemmy.world ⁨2⁩ ⁨weeks⁩ 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.

    source

    • dogs0n@sh.itjust.works ⁨2⁩ ⁨weeks⁩ ago

      100% agree, my server has pretty much nothing except docker installed on it and every service I run is always in containers.

      Setting up a new service is mostly 0% risk and apps can’t bog down my main file system with random log files, configs, etc that feel impossible to completely remove.

      I also know that if for any reason my server were to explode, all I would have to do is pull my compose files from the cloud and docker compose up everything and I am exactly where I left off at my last backup point.

      source
• neidu3@sh.itjust.works ⁨3⁩ ⁨weeks⁩ 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.

  source
• billwashere@lemmy.world ⁨2⁩ ⁨weeks⁩ 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 this things sandboxed makes it SO much easier.

  source
• sylver_dragon@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

  I started self hosting in the days well before containers (early 2000’s). Having been though that hell, I’m very happy to have containers.
  I like to tinker with new things and with bare metal installs this has a way of adding cruft to servers and slowly causing the system to get into an unstable state. That’s my own fault, but I’m a simple person who likes simple solutions. There are also the classic issues with dependency hell and just flat out incompatible software. While these issues have gotten much better over the years, isolating applications avoids this problem completely. It also makes OS and hardware upgrades less likely to break stuff.

  These days, I run everything in containers. My wife and I play games like Valheim together and I have a Dockerfile template I use to build self-hosted serves in a container. The Dockerfile usually just requires a few tweaks for AppId, exposed ports and mount points for save data. That paired with a docker-compose.yaml (also built off a template) means I usually have a container up and running in fairly short order. The update process could probably be better, I currently just rebuild the image, but it gets the job done.

  source

  • Auli@lemmy.ca ⁨3⁩ ⁨weeks⁩ ago

    Yes containers have made everything so easy.

    source
• SpookyMulder@twun.io ⁨3⁩ ⁨weeks⁩ ago

  No, you’re not looking to understand. You’re looking to persuade.

  source

  • kiol@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

    What do you mean?

    source

    • WhyJiffie@sh.itjust.works ⁨3⁩ ⁨weeks⁩ ago

      I think this is like sepi’s response but less polite

      source

      • -> View More Comments
• savvywolf@pawb.social ⁨3⁩ ⁨weeks⁩ ago

  I’ve always done things bare metal since starting the selfhosting stuff before containers were common. I’ve recently switched to NixOS on my server, which also solves the dependency hell issue that containers are supposed to solve.

  source
• kutsyk_alexander@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

  I use Raspberry Pi 4 with 16GB SD-card. I simply don’t have enough memory and CPU power for 15 separate database containers for every service witch I want to use.

  source

  • comrade_twisty@feddit.org ⁨3⁩ ⁨weeks⁩ ago

    Databases on sd cards are a nightmare for sd card lifetimes. I would really recommend getting at least a USD SSD stick instead if you want to keep it compact.

    Your SD card will die suddenly someday in the near future otherwise.

    source

    • kutsyk_alexander@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

      Thank you for your advice. I do use a external hard drive for my data.

      source
  • kiol@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

    So, are you running 15 services on the Pi 4 without containers?

    source

    • kutsyk_alexander@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

      The list of what I run on my RPi:

      • pi.alert
      • fail2ban
      • vftpd
      • samba
      • NFS
      • nextcloud
      • syncthing
      • squid proxy cache
      • PiVPN
      • pi-hole
      • gitea
      • classquiz
      • ntfy
      • redis
      • motioneye
      • vaultwarden

      Some of them runs in containers, some of them runs on bare metal.

      source

      • -> View More Comments
• HiTekRedNek@lemmy.world ⁨2⁩ ⁨weeks⁩ 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.

  source

  • AA5B@lemmy.world ⁨2⁩ ⁨weeks⁩ 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

    source

    • Damage@feddit.it ⁨2⁩ ⁨weeks⁩ 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.

      source

      • -> View More Comments
• FreedomAdvocate@lemmy.net.au ⁨2⁩ ⁨weeks⁩ ago

  Containerisation is all the rage, but in reality it’s not needed at all for all but a tiny number of self hosters. If a native program option exists, it’s generally just easier and more performant to use that.

  Docker and the like shine when you’re frequently deploying and destroying. If you’re doing that with your home server you’re doing it very wrong.

  I like docker, I use it on my server, but I am more and more switching back to native apps. There’s just zero advantage to running most things in docker.

  source

  • donalonzo@lemmy.world ⁨2⁩ ⁨weeks⁩ ago

    Containers are as performant as a native program because they are native programs.

    source

    • FreedomAdvocate@lemmy.net.au ⁨2⁩ ⁨weeks⁩ ago

      Nope. If you use docker containers on windows or mac, they’re running using an abstraction layer. Docker is the native app, but what’s running inside them isn’t. At best they are nearly identical in performance with negligible hit to performance, but as soon as you use things like port forwarding the performance takes a hit.

      stackoverflow.com/…/what-is-the-runtime-performan…

      source
• Strider@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

  Erm. I’d just say there’s no benefit in adding layers just for the sake of it.

  It’s just different needs. Say I have a machine where I run a dedicated database on, I’d install it just like that because as said there’s no advantage in making it more complicated.

  source
• kiol@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

  Are you concerned about your self-hosted bare metal machine being a single point of failure? Or, are you concerned it will be difficult to reproduce?

  source

  • 30p87@feddit.org ⁨3⁩ ⁨weeks⁩ ago

    Considering I have a full backup, all services are Arch packages and all important data is on its own drive, I’m not concerned about anything

    source
• nuggie_ss@lemmings.world ⁨2⁩ ⁨weeks⁩ ago

  Warms me heart to see people in this thread thinking for themselves and not doing something just because other people are.

  source
• sj_zero ⁨2⁩ ⁨weeks⁩ 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 ⁨2⁩ ⁨weeks⁩ 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.

    source
• Smokeydope@lemmy.world ⁨2⁩ ⁨weeks⁩ ago

  Im a hobbiest who just learned how to self host my website over the summer. I didn’t know anything so I went with what I knew which is a fresh install of linux and installing from the package manager. As im getting more serious im starting to take another look at docker. Unforunately my OS package manager only has old outdated versions of docker I may need to reinstall with like ubuntu/debian LTS server something with more cutting edge software in repo. I don’t care much for building from scratch and navigating dependency roulette.

  source

  • kiol@lemmy.world ⁨2⁩ ⁨weeks⁩ ago

    What OS are you using?

    source

    • Smokeydope@lemmy.world ⁨2⁩ ⁨weeks⁩ ago

      Linux Mint 22

      source

      • -> View More Comments
• Evotech@lemmy.world ⁨2⁩ ⁨weeks⁩ 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.

  source
• pedro@lemmy.dbzer0.com ⁨2⁩ ⁨weeks⁩ ago

  I’ve not cracked docker yet. I don’t get how I backup my containers and their data. I would also need to transfer my Plex database into its container while switching from windows to Linux, I love Linux but haven’t figured out these two things yet

  source

  • hperrin@lemmy.ca ⁨2⁩ ⁨weeks⁩ ago

    Anything you want to back up (data directories, media directories, db data) you would use a bind mount for to a directory on the host. Then you can back them up just like everything else on the host.

    source
• melfie@lemy.lol ⁨3⁩ ⁨weeks⁩ ago

  I use k3s and enjoy benefits like the following over bare metal:

  • Configuration as code where my whole setup is version controlled in git
  • Containers and avoiding dependency hell
  • Built-in reverse proxy with the Traefik ingress controller
  • Declarative network policies with Calico, mainly to make sure nothing phones home
  • Managing secrets securely in git with Bitnami Sealed Secrets
  • Liveness and readiness probes that automatically “turn it off and on again” when something goes wrong

  These are just the benefits just for one server. Add more and the benefits increase.

  source
• yessikg@fedia.io ⁨2⁩ ⁨weeks⁩ 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

  source