Comment on Proxmox or NAS for Media Server
talbot@lemmy.world 11 months ago
Running a Debian VM with Docker solved all those issues for me. I set the arrs root /data folder on my NAS to mount with CIFS at boot. It works so well with a ceiling of 4/8 cores and 12GB RAM I’ve moved all my containers to it and mostly just use Proxmox for monitoring and reliable backups/images over NFS.
The only issue I’ve had in the last year or so took me about 30 minutes between realizing something was wrong and fixing it: Make sure you put your CIFS credentials file in a folder accessible to Debian’s main user account or a power loss will break automount until you re-establish the link with a root user. Or create a locked down arrs-only user on your NAS so the CIFS command can include the username and password with less concern.
thirdBreakfast@lemmy.world 11 months ago
I have a very similar setup. Jellyfin in Docker on a Debian VM (2 cores, 8GB RAM), and all the media on the NAS. The CIFS/SMB from the NAS is mounted in fstab. I keep all the metadata locally for speed - ie not on the NAS. I don’t like the extra layer of running Docker, but it works like a charm whereas I had a few hassles running Jellyfin natively in the VM. I do have a special ‘media’ user with the name and password in the mount command which only has permissions for the media.
Can’t comment on the arrs suite since I get all my linux distros on those disks attached to the front of magazines.