this post was submitted on 24 Sep 2025
153 points (94.7% liked)

Selfhosted

51863 readers
581 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
 

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
[–] ChapulinColorado@lemmy.world 1 points 4 days ago (1 children)

I would give docker compose a try instead. I found Proxmox to be too much, when a simple yaml file (that can be checked into a repo) can do the job.

Pay attention to when people say things can be improved (secrets/passwords, rootless/podman, backups), etc. And come back to them later.

Just don't expose things to the internet until you understand the risks and don't check in secrets to a public git repo and go from there. It is a lot more manageable and feels like a hobby vs feeling like I'm still at work trying to get high availability, concurrency and all this other stuff that does not matter for a home setup.

[–] lka1988@lemmy.dbzer0.com 2 points 4 days ago* (last edited 4 days ago) (1 children)

I would give docker compose a try instead. I found Proxmox to be too much, when a simple yaml file (that can be checked into a repo) can do the job.

Proxmox and Docker serve different purposes. They aren't mutually exclusive. I have 4 separate VMs in my Proxmox cluster dedicated specifically to Docker; all running Dockge, too, so the stacks can all be managed from one interface.

[–] ChapulinColorado@lemmy.world 2 points 4 days ago (1 children)

I get that, but the services listed by the other comment run just fine in docker with less hassle by throwing in some bind mounts.

The 4 VMs dedicated dockge instances is exactly the kind of thing I had in mind for people that want to avoid something that sounds more like work than a hobby when starting out. Building the knowledge takes time and each product introduced reduces the likelihood of it being completed anytime soon.

[–] lka1988@lemmy.dbzer0.com 2 points 4 days ago* (last edited 4 days ago)

Fair point. I'm 12 years into my own self-hosting journey, I guess it's easy to forget that haha.

When I started dicking around with Docker, I initially used Portainer for a while, but that just had way too much going on and the licensing was confusing. Dockge is way easier to deal with, and stupid simple to set up.