this post was submitted on 04 Jul 2023
92 points (97.9% liked)

Selfhosted

42670 readers
567 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'm thinking about starting a self hosting setup, and my first thought was to install k8s (k3s probably) and containerise everything.

But I see most people on here seem to recommend virtualizing everything with proxmox.

What are the benefits of using VMs/proxmox over containers/k8s?

Or really I'm more interested in the reverse, are there reasons not to just run everything with k8s as the base layer? Since it's more relevant to my actual job, I'd lean towards ramping up on k8s unless there's a compelling reason not to.

(page 2) 18 comments
sorted by: hot top controversial new old
[–] GustavoM@lemmy.world 1 points 2 years ago

VMs if you have enough RAM and/or need to run something on a non-compatible system (like pfsense on ARM). Containers for everything else.

[–] Midou@kbin.projectsegfau.lt 1 points 2 years ago* (last edited 2 years ago)

If it's relevant to your actual job, learning to use k8s will benefit you more. Generally i'd prefer to keep the bare metal OS as clean as possible to avoid breaking anything during upgrades and such, and keep the containers and normal running apps on separate VMs that can communicate with eachothers, k8s is mostly good if you got a lot of servers and want to manage them all at once through a single "orchestrator". But for self hosting stuff in your home it's kinda overkill. But it still can be used to manage things up. So imo go for k8s since it can be used in homeservers, it's just that it's kinda like using a nuclear bomb to kill a wasp.

I have a pretty low power server at home (Pentium G4560), and the previous one was even slower J3160, so I don't want to unnecessarily hog the CPU with a VM, and the few services I need at home run perfectly fine in containers.

I run pihole, unbound, wireguard, plex, unifi controller in containers, and I run some additional services directly on the host (samba, transmission).

I have a Windows VM on my Windows PC for work, so it's isolated from my main rig (various VPN clients and work files etc), and if I needed some Linux stuff on my Windows PC I'd also run a VM, but more VMs also mean more updating and patching, which is much easier with containers.

[–] smolgumball@lemmy.blahaj.zone 1 points 2 years ago

also curious abt this

[–] Samsy@lemmy.ml 1 points 2 years ago

You can try casaOS.

https://github.com/IceWhaleTech/CasaOS

Its something like k8s. But it is easy to use and works very well with docker containers.

[–] alteredEnvoy@feddit.ch 0 points 2 years ago

I am more comfortable using Ansible and Terraform, so I find VMs more suited for me. Though for random nodejs or PHP apps, I do put them in postman containers and pods.

load more comments
view more: ‹ prev next ›