Selfhosted

60887 readers

1029 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:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

151

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 10 months ago* (last edited 10 months ago) by kiol@lemmy.world to c/selfhosted@lemmy.world

187 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

[–] sem@lemmy.blahaj.zone 10 points 10 months ago (1 children)

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

[–] billwashere@lemmy.world 11 points 10 months ago (1 children)

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.

[–] dogs0n@sh.itjust.works 6 points 10 months 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.