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.
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.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
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).
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.
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.