I have CasaOS and I installed this https://hub.docker.com/r/linuxserver/overseerr
Is there an easy way to simply upgrade it like a normal update and keep the settings?
Here is a migration guide from the devs: https://docs.seerr.dev/migration-guide
If I understand it, Docker users just need to update the compose file and the settings should migrate. But I haven’t done this yet and I’ll definitely be backing up first.
It’s more than that, you have to make sure a certain directory is owned by the “node” user and it has to have uid 1000. That’s a small but very important step in said migration guide, which I overlooked initially. Nothing happened though, container wouldn’t start and its logs kept pointing to this directory, then I saw it in the docs.
Change your compose file image to the new one? That is what I did.
---
services:
seerr:
image: ghcr.io/seerr-team/seerr:latest
CasaOS is like a frontend for Docker, it has an “app store” where it’s just a handful of clicks to install something.
Anyway, I did see that guide but the steps for Docker just say “Refer to Seerr Docker Documentation” which is well, kind of complicated.
I do have Portainer and knkow my way around it’s basics if it makes it easier.
CasaOS doesn’t have a way to do that, how can I do that in Portainer?
Does CasaOS has a way to mount local folders on containers? if that’s so, the only thing you should do is first, stop Overseerr, then install Seerr, point Seerr’s config folder to the same local folder as Overseerr, and run it. Seerr will migrate the configuration and everything will be as if you haven’t installed anything new, Seerr looks and behaves exactly as Overseerr. Then you can delete your Overseerr installation, but make sure that process doesn’t delete any local configuration.
If you have portainer, it should be relatively easy.
First make a backup of the old config folder (I just copied mine to a new seerr folder) then you insert your current data into the docker compose-file they show at your link and import that as a stack. Boom, done.
If you have an existing stack with, let’s say, radarr and sonarr and plesk and overseerr, then you can backup the old compose file, and replace only the overseer part with the code from the given compose config.
I really hope they come up with a better solution for that. My whole arr stack is linuxserver based with the common PUID PGID variables and Seerr is the only one that does it like this. (I often move my stack around for testing purposes)
ok great thank you!
Can’t you just do a new setup? I just installed the seerr container on my unraid server and it took just a couple of minutes. Or am I missing something?
yeah, it really sucks to spring this upon as like this… I had to change UID/GID of a user too because of that, really annoying.