Sonarr 4

[Dulanic]

Have you considered adding sonarr 4 as an option for sonarr install? It is so much better, and I was just transitioning to proxmox from docker, and I used it there. I only realized this wasn't the same version when I restored my backup, and it complained about a missing column :) Maybe making it a choice as to which version to use during install?

[tteck]

Is there an install path? All that I can find is

wget -q https://download.sonarr.tv/v4/develop/4.0.0.646/Sonarr.develop.4.0.0.646.linux-x64.tar.gz
tar -xzf Sonarr.develop.4.0.0.646.linux-x64.tar.gz

Which looks like you need to move/overwrite files.

[DocDrydenn]

This is all I could find on it. forum

[Dulanic]

LSIO and Hotio have it, could probably see what they do?

https://github.com/linuxserver/docker-sonarr/blob/master/Dockerfile
https://hotio.dev/containers/sonarr/

[dhenry437]

Bump. Any further on this? Or could someone point me in the right direction for installing Sonarr 4 using the Debian LXC as a base

[KevinBoone90]

Upvote. I would be very interested in this too! Getting some errors now when downloading metadata, would be resolved according to the developer in the new version.

[KickingAss2024]

Upvote x 2. very interested! The new version is the way as v3 is old news.

[Dulanic]

If you guys want this for now, just run docker in a LXC and run LSIO Sonarr v4.

[tteck]

To upgrade your Sonarr (v3) LXC to Sonarr v4, you can copy and paste all the commands below at once into the Sonarr LXC console:

systemctl stop sonarr.service
wget -q https://download.sonarr.tv/v4/develop/4.0.0.697/Sonarr.develop.4.0.0.697.linux-x64.tar.gz
tar -xzf Sonarr.develop.4.0.0.697.linux-x64.tar.gz
cp -r Sonarr/* /usr/lib/sonarr/bin
rm -rf Sonarr Sonarr.develop.4.0.0.697.linux-x64.tar.gz
sed -i 's|ExecStart=/usr/bin/mono --debug /usr/lib/sonarr/bin/Sonarr.exe -nobrowser -data=/var/lib/sonarr|ExecStart=/usr/lib/sonarr/bin/Sonarr -nobrowser -data=/var/lib/sonarr|' /lib/systemd/system/sonarr.service
systemctl daemon-reload
systemctl start sonarr.service

[towerhand]

Thanks guys

[zelig2]

For those who might want to upgrade their V4 installation I've updated the commands above. Run these commands in your container to upgrade:

systemctl stop sonarr.service
cd /tmp
wget -O SonarrV4.tar.gz 'https://services.sonarr.tv/v1/download/develop/latest?version=4&os=linux'
tar -xzf SonarrV4.tar.gz
cp -r Sonarr/* /usr/lib/sonarr/bin
rm -rf Sonarr SonarrV4.tar.gz
systemctl start sonarr.service

[tteck]

I'll add that to the script

[nicoska84]

I executed those commands but now the Sonarr service is not accessible anymore :(

[AdmiralAwesome]

Running update inside LXC with

bash -c "$(wget -qLO - https://github.com/tteck/Proxmox/raw/main/ct/sonarr.sh)"

Will break your Sonarr installation. Website is no longer available.

[zelig2]

In any circumstance, I can't identify any disadvantages to running as the root user instead of Sonarr.

For me, I prefer to have all the *arr apps run from non-root users in the LXCs. I do that so I can more securely bind my CIFS/SMB shares into the unprivileged containers. Sonarr was the only one who used a specific user for the application so I created unique users for all my *arrs. No need to change the script for me, I'll manage it on my side as it's a somewhat unique configuration.

[Dulanic]

In any circumstance, I can't identify any disadvantages to running as the root user instead of Sonarr.

For me, I prefer to have all the *arr apps run from non-root users in the LXCs. I do that so I can more securely bind my CIFS/SMB shares into the unprivileged containers. Sonarr was the only one who used a specific user for the application so I created unique users for all my *arrs. No need to change the script for me, I'll manage it on my side as it's a somewhat unique configuration.

I think a lot do this. However my workaround was forcing the userid with the NFS export.

[kvmgz]

Hi folks.
I had v3 Sonarr and thought I give it a shot for the v4.
I tried to update using the initial script. It asks me nicely if I want to upgrade to v4. Everything goes without an error, but I can't access Sonarr anymore.
If I do a clean install and choose v4, it works, but I CBA to reconfigure everything.
Any thoughts?

[mitchellmarkly]

I literally just did the same thing, but I believe the script is actually asking "are you updating v4?" as in- you already have v4 installed and are updating. I'm going to try running the commands posted above to upgrade to v4.

*Update: I restored my v3 from a backup and then ran the upgrade commands-worked like a charm.

[kvmgz]

You ran the script or what upgrade command are you referring to?

[towerhand]

@tteck V4 has been published to the main branch.
https://www.reddit.com/r/sonarr/s/139hxxhdIh

Is there anything we need to do on the existing lxcs? Or do we need to wait for an update to your script and create a new lxc?

Thanks.

[AdmiralAwesome]

Is there anything we need to do on the existing lxcs? Or do we need to wait for an update to your script and create a new lxc?

Native versions for Windows, MacOS and Linux have been published and are available to download from sonarr.tv. They will need to be downloaded and installed manually, updates will not happen via Sonarr. Note that x86 releases are no longer available for Linux.

[tteck]

I have completed a major code refactoring of Sonarr v4 to bring it more inline with the mainstream paths (no more upgrading from v3).
This will be a Breaking Change. The previous installs will not be updated via the update command.
The user is now sonarr and the group is media.

[zelig2]

You're correct. I'll build a new LXC at some point in the future to get back to a compliant setup. Due to my user bindings I need to be careful how I set it all up again.

[tteck]

You probably can use the Sonarr install script (listed above) to become compliant.

[kvmgz]

After successfully upgrading and it was working fine, I realised the downloaded files remain in Que and are not copied to the selected destination folder. If I select the files and try to import manually it says completed but it's not doing anything actually.
Obs.: I used a Turnkey Fileserver to which I associated an SSD drive as a makeshift NAS.
I guess it's some kind of permission issue, since between the Sonarr v3 and 4v some user and group info was changed, but tbh I have no idea what to change or add to solve it :|

[ianfriend]

See my comments on this thread #1738 (comment)

It's probably the same issue of permissions where your download client is creating the files are root:root and now after upgrading to v4 your sonarr is trying to access them as sonarr:media

Fix is to run the install script mentioned in that thread and set sonarr to also run as root:root which is what v3 used to run as

[kvmgz]

Yep, tteck's script allowed me to set it back to root:root and all works well.
Thanks for the quick reply mate!

For future ppl lurking here the script was the following:

bash -c "$(wget -qLO - https://github.com/Sonarr/Sonarr/raw/develop/distribution/debian/install.sh)"

[Jarrekstar]

Any way to easily copy over the configuration from the existing v3 instance?

[tteck]

The data path (/var/lib/sonarr) did not change, so you can move the contents.

[Jarrekstar]

Awesome, thanks

[markwoodward86]

FYI i just took a back up of my old v4 application via the Sonarr UI, ran tteck's latest helper script to start a brand new container, then in the new container i restored from previous backup and voila, i am compliant. Easy as pie.

[towerhand]

I agree. I think the other ARRS programs are running as root or used to run as root when I ran the script a little while ago.

[tteck]

f6e17e8

[maxoss]

did a fresh install and it works now, thank

[bdoell88]

Is it possible to apply these changes to an existing install instead of doing a fresh install?

[ianfriend]

Yes that's what I did. Use the install script tteck posed above and install as user and group root

[KevinBoone90]

Anyone else experiencing massive RAM usage for Sonarr v4? Feels like there is a memory leak or something? Currently using 6GB of RAM during scans/searchs...

[ianfriend]

not for me, bumbling along the past week at 150-160MB

[randomparity]

I've been seeing OOM messages on the host that kill sonarr which is configured for 1GB RAM:

[Tue Feb 27 12:13:37 2024] oom-kill:constraint=CONSTRAINT_MEMCG,nodemask=(null),cpuset=pvestatd.service,mems_allowed=0,oom_memcg=/lxc/1003,task_memcg=/lxc/1003/ns/init.scope,task=systemd,pid=3459049,uid=100000 [Tue Feb 27 12:13:37 2024] Memory cgroup out of memory: Killed process 3459049 (systemd) total-vm:167644kB, anon-rss:0kB, file-rss:128kB, shmem-rss:0kB, UID:100000 pgtables:84kB oom_score_adj:0 [Tue Feb 27 12:13:39 2024] oom_reaper: reaped process 3459049 (systemd), now anon-rss:0kB, file-rss:128kB, shmem-rss:0kB

My sonarr version was 4.0.0.740. Sometimes the app is restarted in the container and sometimes I see the container is completely stopped. I'm trying to update now to see if the issue persists.

[AkiVonAkira]

Tried to update Sonarr through the LXC console and the webui, but the first method no longer works and there seems to be a permission issue with the sonarr user.
I would chown but I can't seem to find the startup folder, hehe :p
ty <3

[tteck]

Did you type update in the console?

[KevinBoone90]

Hi tteck, thanks for your reply. Yes did try the update command, same result

[tteck]

This would indicate that you've fallen victim to a breaking change noted here, a3ef98e
To resolve this, you'll need to create a new Sonarr LXC, or continue to use apt update && apt upgrade to keep yours up to date.

Seems that you're using V3

[KevinBoone90]

I am on V4

[tteck]

To resolve this, you'll need to create a new Sonarr LXC.