Selfhosted

51863 readers

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

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

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 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

153

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

185 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

[–] zod000@lemmy.dbzer0.com 3 points 5 days ago (1 children)

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.

[–] renegadespork@lemmy.jelliefrontier.net 1 points 5 days ago (1 children)

Hm, I don't know about that either. While scale is their primary purpose, another core tenant of containerization is reproducibility. For example

If you are developing any sort of software, containers are a great way to ensure that the environment of your builds remains consistent.
If you are frequently rebuilding a server/application for any reason, containers provide a good way to ensure everything is configured exactly as it was before, and when used with Git, changes are easy to track. There are also other tools that excel at this (like Ansible).

[–] zod000@lemmy.dbzer0.com 1 points 5 days ago

That to me still feels like a variety of "scale". All of these tools (Ansible is a great example) are of dubious benefit when your scale of systems is small. If you only have a single dev machine or server, having an infrastructure-as-code system or containerized abstraction layer, just feels to me like unnecessary added mental overhead. If this post had been in a community about FOSS development or general programming, I'd feel differently as all of these things can be of great use there. Maybe my idea of selfhosting just isn't as grandiose as some of the people in here. If you have a room full of server racks in your house, that's a whole other ballgame.