2
Dietpi as a hosting OS (lemmy.perthchat.org)
submitted 3 years ago by to c/selfhosted@lemmy.world
6 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?

you are viewing a single comment's thread
view the rest of the comments
[–] 0 points 3 years ago (1 child)

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.

  • permalink
  • fedilink
  • source
  • hideshow 2 child comments
    •
  • [–] [S] 0 points 3 years ago (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 3 years 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.

  • permalink
  • fedilink
  • source
  • parent