this post was submitted on 08 Sep 2025
68 points (95.9% liked)

Selfhosted

51445 readers
283 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
 

I have a server with a bunch of services just as Docker containers. I see that Proxmox is popular among the self-hosting community. I was wondering why?

I understand that running things in a VM provides better security than running them in a container. But is the difference so important given the relatively low risk that an exploit happens inside a container that leads to doing damage to the host machine?

There's also obviously the additional overhead of using Proxmox. It wouldn't be an issue for me as I should have enough resources to, say replace all my Docker containers with VMs. I'm more wondering if the security difference is so massive, or if there is another reason I'm missing why people use Proxmox.

Or am I misunderstanding how people use Proxmox? I was assuming people would use it like how you use Docker, i.e. different services get their own VM/container. If you have a different kind of setup I'd be interested in hearing it.

Edit: I would appreciate if people stop being pedantic and actually read the post. Obviously I am aware that you can run containers in VMs, or containers on bare metal alongside VMs. That's not what the question is and you know it.

you are viewing a single comment's thread
view the rest of the comments
[–] sugar_in_your_tea@sh.itjust.works 8 points 1 week ago (1 children)

My vote is Podman with an immutable distro, like OpenSUSE MicroOS or Fedora Silverblue. Here are my reasons:

  • rolling base, with very minimal footprint, so you don't need to worry about upgrades
  • podman runs proper rootless containers, so you get better security vs docker, which tends to run as root (breaking out does less damage if you manage permissions properly)
  • deploying a new service (or moving a service) just means copying configs and running, no concerns about what the host has
  • there's nothing special about the host, so if MicroOS or Silverblue are abandoned, just copy the configs and data to a new host

It's a little more work to set up, but once things are running, it's drama free. And I think that's the best thing to optimize for, keeping things boring is a good thing.

[–] atzanteol@sh.itjust.works 4 points 6 days ago

"I run an immutable distro, BTW"