this post was submitted on 24 Jun 2023
3 points (100.0% liked)

Selfhosted

39158 readers
408 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 am looking for some thoughts on using dietpi as a hosting OS.

I am going to use proxmox as a hypervisor (simplify upgrades, IaC, backups etc) on a x86-64 arch. But am looking for the best OS to host on.

I almost exclusively use docker to host the services.

I stumbled across someone suggesting dietpi, and thought what a good idea, a really lightweight OS.

what's peoples experiences using dietpi as a hosting os, outside of SBCs?

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 1 year ago

I am using Dietpi as a VirtualBox image since it is easy for me to configure. I only have a Windows 10 pro machine and I also use it as homemedia server. The wifey does not like Linux, so I cannot run Linux on it. At the same time, my PC spec is not that great, or you can say a potato PC.

It is an Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz 8 GB RAM. Even though it is a potato with Windows running on it, I can manage to run two Dietpi virtual boxes, one running for Pihole and the second for Docker.

The Pihole ran for maybe around 3 years, and there was no problem. While for the docker, I keep changing it and rebuilding it since sometimes I messed up with the docker, so I just rebuilt it because DietPi is easy to deploy and fast. Even with that potato, in under 8 minutes, including setting the IP, local host, region, install docker, Portainer, NPM, etc. I can have a fresh install Dietpi with docker ready to use. That's why I never worry to make mistakes on my docker VM.

That is my experience with Dietpi and the reason why I am still using it, so in my opinion, you can try it. Who knows it will fit your need.