Howdy selfhosters
I’ve got a bit of an interesting one that started as a learning experience but it’s one I think I got a bit over my head in. I had been running the arr stack via docker-compose on my old Ubuntu desktop pc. I got lucky with a recycler and managed to get a decent old workstation and my company tossed out some 15 SAS hdds. Thankfully those worked. I managed to get the proxmox setup finally and got a few drives mounted in a zfs pool that plex presently reads from. I unfortunately failed to manage to save a last backup copy of my old stack, however that one I’ll admit was a bit messy with using gluetun with a vpn tie to a German server for p2p on the stack. I did preserve a lot of my old data though as a migration for the media libraries.
I’m open to suggestions to have the stack running again on proxmox on the work station, I’m not sure how best to go about it with this since accessing a mount point is only accessible via lxc containers and I can’t really figure how to pass the zfs shares to a vm. I feel like I’m over complicating this but needing to maintain a secure connection since burgerland doesn’t make for the best arr stack hosts in my experience. It feels a bit daunting as I’ve tried to tackle it and give a few LLMs to write me up some guidelines to make it easier but I seemed to just not be able to make that work to teach me.
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.
Proxmox isn’t really comparable to Docker (or its 3rd party webui frontends) and was never meant to directly run user-facing services. Proxmox simply provides the virtual infrastructure required to host VMs and LXCs that will run your desired services.
IMO, Dockge (not a typo) is a far cleaner and easier solution than Portainer. Its very simple to set up, and even link to Dockge instances on other Docker hosts. It also doesn’t bury your compose files deep inside a specific Docker volume that only allows its own container to access…like Portainer does.