If you don't actually want to allow external untrusted people accessing your server, why go the VM route? That seems like a huge waste of resources and just complicates things compared to using containers (Podman is best IMHO).
this post was submitted on 14 Jun 2023
3 points (100.0% liked)
Self Hosted - Self-hosting your services.
11440 readers
1 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
- No harassment
- crossposts from c/Open Source & c/docker & related may be allowed, depending on context
- Video Promoting is allowed if is within the topic.
- No spamming.
- Stay friendly.
- Follow the lemmy.ml instance rules.
- Tag your post. (Read under)
Important
Beginning of January 1st 2024 this rule WILL be enforced. Posts that are not tagged will be warned and if not fixed within 24h then removed!
- Lemmy doesn't have tags yet, so mark it with [Question], [Help], [Project], [Other], [Promoting] or other you may think is appropriate.
Cross-posting
- !everything_git@lemmy.ml is allowed!
- !docker@lemmy.ml is allowed!
- !portainer@lemmy.ml is allowed!
- !fediverse@lemmy.ml is allowed if topic has to do with selfhosting.
- !selfhosted@lemmy.ml is allowed!
If you see a rule-breaker please DM the mods!
founded 3 years ago
MODERATORS
I have no problems with untrusted people accessing resources I intend to be public. A VM provides an extra layer of protection in that scenario, as does a container. I’ve been playing with Lemmy containerized in an xcp-ng VM.
But really, it’s a chance to learn and play with something new.
I mean as in renting out servers (VMs), where untrusted people have full root access.
Ah. Yes, I have no plans to do something like that.
My answer still applies. If there’s a remote code exploit that can be used to gain root, running it in a container just gets you root there. Running it in a VM only gets you root there. Both provide layers to protect the underlying OS.
Indeed, VMs are more secure than containers, but they come had a quite heavy price performance wise and are also harder to maintain. With Podman you can manage containers just like any other systemd service, which is really convenient.
Ive tried all the main "Homelab Hypervisors" in my lab. VMWare, HyperV, Proxmox, XCP-NG/XenServer. I always come back to proxmox because it offers all of the features I need (HA and Backups primarily) in an extremely easy to use fashion.
I had a great deal of problems getting XCP-NG/XenOrchestra's backup process to function correctly.
Proxmox Backup Server just works. Its the first time in many years of homelabbing/SysAdmin in general where a solution does what its supposed to without needing to contact support.
I started with Proxmox in my homelab as I was a beginner and the proxmox forums were amazing as a resource to learn about everything proxmox. I decided to stick with it as it was so easy for a beginner like me.
I like Promox for home, and XCP-NG for work. I'm just significantly more resource constrained at the house then work, so container management in the main interface is nice. At work, everything is a VM with containers on top (when needed)