Selfhosted

38768 readers

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

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

[email protected]

Dietpi as a hosting OS (lemmy.perthchat.org)

submitted 1 year ago by [email protected] to c/[email protected]

7 comments fedilink hide all child comments

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?

top 5 comments

sorted by: hot top controversial new old

[–] [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.

[–] [email protected] 0 points 1 year ago

The best OS to host on will someday be NixOS, bar none IMO. However, that BEST title will depend heavily on someone sharing a config that leverages the power of NixOS to make it as foolproof and rock-solid as other projects that leverage Nix’s power and reliability.

I’d host an instance if we could would move from the world of Docker being the only game in town toward a more reproducible standard config that uses Nix.

[–] [email protected] 0 points 1 year ago (1 children)

I am a bit confused. You said you were going to use Proxmox. It is a hypervisor built on top of Debian. Good choice btw. Why do you need another hosting OS? Proxmox runs the VMs and LXCs and is naturally your hosting OS.

[–] [email protected] 0 points 1 year ago (1 children)

I am looking at proxmox to create the VMs, of which I am considering dietpi.

Note, I am addicted to docker, and whilst I would love to run a bunch of containers within LXC, from my research, it is problematic and unfortunately I don't have time at the moment to learn the intricacies of LXC <> docker.

I like the idea of LXC minimal OS.

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago)

Oh okay I get what you mean now.

If your Proxmox machine is not stingent in resources (e.g. storage, memory, etc), I would recommend sticking to distros you find more familiar with. Popular distros such as Debian, Ubuntu, and Arch are also fine. I don't think the overhead is that pronounced.

I have been running docker in LXC (Ubuntu server 22.04 image for the LXC + Official Docker installation, i.e. not Snap) and so far I have not encountered any roadblock from the intricacies between LXC and Docker. Usually they are from within the docker images and the embedded networks. But I am not centralizing all Docker affairs into one LXC. I split them by services. So your mileage may vary.

load more comments