62
Running arr services on a proxmox cluster to download to a device on the same network. I don’t think there would be any problems but wanted to see what changes need to be done.
I'm essentially doing this with my set up. I have a box running proxmox and a separate networked nas device. There aren't really any changes, per se, other than pointing the *arr installs at the correct mounts. One thing to make note of, i would make sure that your download, processing, and final locations are all within the same mount point, so that you can take advantage of atomic moves.
I second this. It took me a really long time how to properly mount network storage on proxmox VM's/LXC's, so just be prepared and determine the configuration ahead of time. Unprivilaged LXC's have differen't root user mappings, and you can't mount an SMB directly into a container (someone correct me if i'm wrong here), so if you go that route you will need to fuss a bit with user maps.
I personally have a VM running with docker for the arr suite and a separate LXC's for my sambashare and streaming services. It's easy to coordinate mount points with the compose.yml files, but still tricky getting the network storage mounted for read/write within the docker containers and LXC's.
Do two NICs. I have a bigger setup, and it's all running on one LAN, and it is starting to run into problems. Changing to a two network setup from the outset probably would have saved me a lot of grief.
Can you explain what benefit that would bring?
load more comments
(17 replies)
I have two Proxmox hosts and two NASes. All are connected at 1Gbps.
The Proxmox hosts maintain the real network mounts - nfs in my case - for the NAS shares. Inside each CT that requires them, these are mapped to mount points with identical paths in each, eg. /storage/nas1 and /storage/nas2.
All my *arr (and downloader) CTs are configured to use the exact same paths.
It's seamless. nzbget or deluge download to the same parent folders that my *arr CTs work with, which means atomic renames/moves are pretty much instant. The only real network traffic is from the download CTs to the NASes.
Edit: my downloader CTs download directly to the NAS paths - no intermediate disk at all.
I have a setup similar to what you want.
My nas is a low powered atom board that runs unraid.
My dockets run on a ryzen CPU with proxmox. I don't have a cluster, just 1.
In proxmox I run a VM that runs a all my dockets.
I use portainer to run all my services as stacks. So the arr stack has all the arrs together in a docker compose file. The docker compose files are stored in gitea (one of the few things I still run on unraid) and Everytime I make a change to the git, I press one button on portainer and it pulls down the latest docker compose.
For storage, on proxmox I use zfs with ssds only. The only thing that needs HDDs is the media on my unraid.
When a docker needs to access the media it uses an NFS mount to the unraid server.
Everything else is on my zfs array on proxmox. I have auto zfs snapshots every hour. Borg backup also takes hourly incremental backups of the zfs array and sends it to the unraid server locally and borg base for off-site backup.
The whole setup works very well and it very stable.
The flexibility of using proxmox means that things that work better in a VM (HaOS) I can install as a VM. Everything else is docker.
Use ZFS when prompted - it opens up some features and is a bitch to change later. I don't understand why it's not the default.
load more comments
(3 replies)
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:
| Fewer Letters | More Letters |
|---|---|
| Git | Popular version control system, primarily for code |
| HTTP | Hypertext Transfer Protocol, the Web |
| IP | Internet Protocol |
| LXC | Linux Containers |
| NAS | Network-Attached Storage |
| SSD | Solid State Drive mass storage |
| ZFS | Solaris/Linux filesystem focusing on data integrity |
| k8s | Kubernetes container management package |
| nginx | Popular HTTP server |
8 acronyms in this thread; the most compressed thread commented on today has 8 acronyms.
[Thread #411 for this sub, first seen 8th Jan 2024, 20:15] [FAQ] [Full list] [Contact] [Source code]
For your Proxmox cluster shoot for three devices. With three devices you can do high availability which is a bonus but not something I though to do when I built my setup.
And you don't have quorum issues any time a system is down. (I regret making mine a cluster.)
You can set up a qdev on a pi or something.
Can you? That would be really cool
Yeah, you can run it on anything and its great for even numbered clusters.
Can you explain how?
I need to re-ip both of my proxmox hosts and ran into a wall due to quorum. This could get me over that hump.
That being said, it was a failed experiment to put them in a cluster. I don't use any of the cluster functionality and would love to destroy the cluster config w/o having to rebuild the proxmox hosts.
load more comments
(2 replies)
Consider checking out XCP-ng. I've been testing it for a few days and I'm really enjoying it. Seems less complicated and more flexible than Proxmox but admittedly I'm still learning and haven't even tried multiple servers yet. I would suggest watching some YouTube videos first. Good luck!
I want to like XCP-ng. Unfortunately my primary use case is VMs or containers working with attached USB devices. On Xen it seems like an absolute nightmare to passthrough USB or PCI devices other than GPUs (as vGPUs).
Even on Proxmox it has been frustratingly manual.
I'm planning to try out k8s generic device plugins. I don't really need VMs if containers will cooperate with the host's USB. I'm sure that will be a bit of a nightmare on its own and I will be right back to Proxmox.
I hope someone will tell me I am wrong and USB can be easy with Xen. I do prefer XCP-ng over Proxmox in many other ways.
Here's their documentation. The tip suggests it may have been harder in the past but it doesn't seem too bad now. Hopefully this is configurable in Xen Orchestra in the future.
My current setup is 3x Lenovo m920q (soon to be 4) all in a proxmox cluster, along with a qnap nas with 20gb ram and 4x 8tb in raid 5.
The specs on the m920q are: I5 8500T 32gb ram 256gb sata SSD 2tb nvme SSD 1gbe nic
On each proxmox machine, I have a docker server in swarm mode and each of those vm all have the same NFS mounts pointing to the nas
On the Nas I have a normal docker installation which runs my databases
On the swarm I have over 60 docker containers, including the arr services, overseerr and two deluge instances
I have no issues with performance or read/write or timeouts.
As one of the other posters said, point all of your arr services to the same mount point as it makes it far easier for the automated stuff to work.
Put all the arr services into a single stack (or at least on a single network), that way you can just point them to the container name rather than IP, for example, in overseerr to tell it where sonarr is, you'd just say http://sonarr:8989 and it will make life much easier
As for proxmox, the biggest thing I'll say from my experience, if you're just starting out, make sure you set it's IP and hostname to what you want right from the start... It's a pain in the ass to change them later. So if you're planning to use vlans or something, set them up first
this post was submitted on 08 Jan 2024
62 points (100.0% liked)
Selfhosted
42834 readers
744 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:
- 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