this post was submitted on 26 Jul 2023
23 points (87.1% liked)

Selfhosted

40347 readers
330 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 1 year ago
MODERATORS
 

I have an old x86_64 computer which I am planning to use as a NAS. Which of the 2 is a better option? Is it helpful or better to run on bare metal or as a VM on proxmox?

you are viewing a single comment's thread
view the rest of the comments
[–] InverseParallax@lemmy.world 1 points 1 year ago

The rules now are generally: bare metal if that's all the box will do, or it's main task, container if it's one of many services, vm if it's a larger application you might migrate and i/o isn't your limitation.

The line between container and vm is fuzzy, but bare metal means you're making a design choice for that machine and if that or another application breaks the machine you're screwed.

In a way freebsd is amazing for this, you put all applications in jails and don't use the main userspace much, but the virtualiztion story isn't quite there yet.