Selfhosted

51445 readers

292 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

Proxmox or Docker? (lemmy.ml)

submitted 1 week ago* (last edited 6 days ago) by communism@lemmy.ml to c/selfhosted@lemmy.world

39 comments fedilink hide all child comments

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

[–] communism@lemmy.ml 2 points 1 week ago (1 children)

I think in general people start out in VMs and advance to containers. If you are already using containers stick with it, otherwise you are taking a step back.

Interesting perspective—I had thought that running an entire VM would be more difficult, but I've never used virtualisation for server stuff, only ever used VMs with a GUI VM manager on my personal computer. Thanks for the input.

[–] 4am@lemmy.zip 9 points 1 week ago

VMs on a server are great fun, and there are some use cases where you’d absolutely need them (as parent said, running Windows on a Linux server, etc). I virtualized my whole-network router using virtualized OPNSense which is BSD based.

If you aren’t into spending time (and, eventually , money) on a setup that does “everything”, you don’t need Proxmox.

But it’s fucking AWESOME for tinkering. I think the question to ask yourself is, do you want a homelab, or do you want to just set-it-and-forget-it?

If you want services to be there without spending time on it, keep it simple. If you want the power that added complexity brings, and you have the means (time/energy/maybe money for upgrades etc) then by all means take the leap. It’s fun as hell, if you’re into it.