Selfhosted

54041 readers

1011 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.
No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Proxmox with arr (lemmy.dbzer0.com)

submitted 3 days ago by standarduser@lemmy.dbzer0.com to c/selfhosted@lemmy.world

26 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[–] Bronzie@sh.itjust.works 3 points 1 day ago (1 children)

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.

[–] PeriodicallyPedantic@lemmy.ca 1 points 20 hours ago (1 children)

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 🤞

[–] Bronzie@sh.itjust.works 2 points 12 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!