Register for the iXsystems Community to get an ad-free experience and exclusive discounts in our eBay Store.

Should we NOT be using the build in updater with Sonarr and Radarr?


FreeNAS Aware
Jul 4, 2015
I am reading with the new iocage plugins that at least for plex we should not be using scripts or updating them manually but instead waiting for the plugin maintainer to update them. Is this across the board such as with Sonarr and Radarr even though they have a built-in updater?


Storage Engineering
May 24, 2011
There is no reason "NOT" to do this. The update method is up to the user to decide which best matches their workflow/use case.


FreeNAS Experienced
Jul 9, 2019
And that is the good thing with a ZFS filesystem. Make a snapshot of the plugin, do the update
and if it does not work simply roll back.


FreeNAS Expert
Jan 1, 2016
Just to be perfectly clear on this...

The built-in updater doesn't update anything about the jail system, just the git code of the project (sonarr, radarr, whatever).

Dependencies that will be covered with a pkg update && pkg upgrade don't get touched if you just do the built-in updates, but may (or may not) be expected or needed by those upgrades (of things like mono, php, java, compression tools and so on).

Again separate is the release/version of the jail itself 11.2-RELEASE, presumably at some point 11.3-RELEASE and so on...

Don't be fooled into thinking your jail is up to date having just updated the application via the web interface.

That said, snapshots and rollback are great and you should feel (mostly) free to go nuts trying stuff and rolling back when you don't like the outcome. Just beware of changes that hit your database and take time to notice, so you may have stepped forward of your snapshot and not want to lose the progress/watched status or whatever by rolling it back to the status of before the changes... anyway, you're all big and bad enough to look after yourselves with that kind onf thing, so have at it.

The plugin updater will probably be doing some work to ensure dependencies step up along with the application, so it's an easier way to ensure a smooth ride if that's all you're looking for.