Comment

PeriodicallyPedantic@lemmy.ca ⁨2⁩ ⁨days⁩ ago

I was recently trying out proxmox and found it super overkill and complex for serving stacks of software.
I switched to portainer and it was so much nicer to work with for that use case.

The one thing I miss is that proxmox can be packaged as an OS so you don’t need to worry about any setup. But I wrote a little script I can use to install portainer and configure systemd to make sure it’s always running.

I just started with portainer so I’m not an expert, but you may want to look into it.

source

Sort:hotnew top

Bronzie@sh.itjust.works ⁨1⁩ ⁨day⁩ ago
Yeah it’s a bit of an unfair comparison that. Hypervisor VS conainer manager.
The reason you run Proxmox is to do «everything» in one place, including docker.

If all you host are containers, then I agree it’s overkill, but if you want VM’s and containers combined, maybe even in a cluster, then Proxmox is hard to beat.

I host LXC’s with Portainer inside Proxmox, as I find it easier to deal with and maintain. Then in a VM I run the full HomeAssistant OS instead of the Docker image.

Unless you don’t need it at all, I’d recommend you give it another try. It’s a very flexible system that «does it all» once you get going.

source
- PeriodicallyPedantic@lemmy.ca ⁨1⁩ ⁨day⁩ ago
  I understand they have different purposes, but one (container manager) seems far more suited to the typical things that people want to do in their homelabs, which is to host applications and application stacks.
  Rarely do I see people need an interactive virtualized environment (in homelabs), except to set up those aforementioned applications, and then containers and containers stack definitions are better because having declarative way to deploy applications is better. Self-hosting projects often provide docker/OCI containers and compose files as the official way to deploy. I’m not deep in the community yet, but so far that has been my experience.
  Additionally, some volume mounting options I wanted to use are only available via CLI, which is frustrating.
  So I don’t really understand what value proposition proxmox provides that has causes homelabs folks to rally around it so passionately.
  
  Having a one-stop-shop that can run VMs is handy for those last-resort scenarios where using an application container just isn’t possible, but thankfully I haven’t run into that yet. It doesn’t seem like OP has run into that yet either, if I read it correctly.
  I’m not deep into my self-hosting journey, but it doesn’t seem like there are that many things that require a VM for hypervisor 🤞
  
  source
  - Bronzie@sh.itjust.works ⁨19⁩ ⁨hours⁩ ago
    You’re not wrong, but I think you might be leaving some future capabilities on the table, that’s it.
    There is nothing wrong with running everything through Portainer at all. It’s how I started myself. The downside is that it’s limited if you ever wish to do e.g. HA OS or a sandboxed OS for testing/playing around. Automatic backups, re-sizing LXC’s or giving more memory is also easier to do with a GUI than in CLI. At least for me hehe.
    
    That’s the great thing about self hosting though: if you’re happy with it, then it’s perfect!
    Don’t change anything because someone tells you to if it works for you, friend!
    
    source
lka1988@sh.itjust.works ⁨1⁩ ⁨day⁩ ago
IMO, Dockge is a far cleaner and easier solution for managing Docker containers than Portainer. Plus, Dockge doesn’t bury your compose files deep inside nested directories that only allows its own container to access…like Portainer does.

source
- PeriodicallyPedantic@lemmy.ca ⁨1⁩ ⁨day⁩ ago
  Yeah I looked into dockge and I really like it, but I still went with portainer because it manages volumes directly rather than having to mount it manually and modify fstab.
  
  I have to admit I don’t really understand the philosophy or value proposition of portainer as it relates specifically to homelabs, because I don’t really understand the value of VMs or LXCs except as last resorts (when you can’t make an application container, since defining applications declaratively almost always better).
  Almost everything I want to host, and I see people talking about hosting in their homelabs, are stacks of applications, which makes something like docker compose perfect for purpose.
  
  When I saw proxmox supported OCI containers, I was hopeful it’d provide a nice way to deploy a stack of OCI containers, but it didn’t. And in fact, some volume mounting features (that I wanted) could only be accessed by CLI.
  
  source