Selfhosted

60543 readers

405 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:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post.

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 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

VMs or containers? (lemmy.world)

submitted 3 years ago by rpn@lemmy.world to c/selfhosted@lemmy.world

75 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[–] brad@toad.work 14 points 3 years ago (1 children)

I, personally, haven't done a whole lot of VM work but I do run a metric ass-ton of containers. I can spool up servers in docker compose on absolutely dogshit hardware and have it run serviceably. Also, the immutability of the container OS is really nice for moving things around and/or getting them set up quickly.

[–] stark@qlemmy.com 2 points 3 years ago (2 children)

Where did you learn so much about Docker? Having a server at home, I'm more inclined to spin up a VM. I would like to learn more about Docker.

[–] brad@toad.work 7 points 3 years ago

If I'm honest, I've stumbled nose-first through pretty much everything I know. I am never afraid to break things as long as I learn from it.

[–] soldersmoker@reddthat.com 2 points 3 years ago* (last edited 3 years ago)

Just get started somewhere. I ran traditional VMs for most things before and I would never go back unless it was necessary for something.

Easiest way is just to start using Docker for some service you're hosting that has a public image available and go from there. If you want a more visual approach there's stuff like Portainer you can use too.

Also get started early on with docker compose, it makes it much easier to organize your container configs.