this post was submitted on 24 Sep 2025
150 points (95.7% liked)

Selfhosted

51810 readers
617 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
ruud@lemmy.world
CannaVet@lemmy.world
Loki@lemmy.world
HybridSarcasm@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
150
Those who are hosting on bare metal: What is stopping you from using Containers or VM's? What are you self hosting? (lemmy.world)
submitted 3 days ago* (last edited 3 days ago) by kiol@lemmy.world to c/selfhosted@lemmy.world
180 comments fedilink hide all child comments
 

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?

you are viewing a single comment's thread
view the rest of the comments
[–] AA5B@lemmy.world 4 points 2 days ago* (last edited 2 days ago) (1 children)

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 2 points 2 days ago (1 children)

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 3 points 2 days 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