#Migrating Overseer to Seer

47 messages · Page 1 of 1 (latest)

spiral moth
#

Sorry if I missed this, but are there step by step instructions on how to migrate overseer to the new Seer beta? I am using docker on Windows and would like to preserve settings.

west canyon
#

Its not released yet.

spiral moth
#

Thanks. Would it be beneficial to migrate to jellyseer in the interim?

lapis rune
spiral moth
#

Ok. Is there a guide for that?

west canyon
#

Ifnyou want to test that is

#

Guide will be out when its officially released

lapis rune
#

Use the same config folder that overseerr used

#

It will work with the old config files

quartz comet
#

Cool I joined the discord looking to see if this was possible. overseerr broke a while ago for me and no longer works with sonarr/radarr apis

#

rip nope it's not a drop-in replacement. keeps restarting

quartz comet
#

ah the api breaking was a combined ssl+network issue for me. sadly seerr not a drop in replacement for overseerr but hopefully in the future it will be

west canyon
#

Its a drop in replacement.

#

Without knowing what issue you're facing we cannot tell.

#

But its a drop in replacement. (Everyone else is using it).

#

You also need to do this:
#seerr-beta message

#

These will be documented in the migration guide which will be released when seerr is released.

quartz comet
#

ah cool thanks the chown worked. that's what was causing the docker image to be stuck in a restart loop

quasi sun
#

does seer not respect permissions, at least in teh docker compose context of UID /GID ? overseer did but seer doesn't seem to. i checked by making a fresh persistent directory for the data, and it made the files and sub-dirs with my primary user id (1000:1000) ..... previously i used docker compose PUID and PGID to specify what user:group numbers to use in overseer, but when i use those in seer it just errors at container startup... just wondering it its a known thing?

#

overseerr would just make the files in its data happily in the root data directory I specifiy with theinitial permissions and using the PUID/PGID I specified in the compose file, 100:100

quasi sun
#

fixed my problems by using chown on the root data dir recursively and the files within from 100:100 to 1000:1000

scenic iris
#

Hey yes it's expected and it's not a bug see (it's documented in the migration guide)
#seerr-beta message

quasi sun
west canyon
#

Its for security reasons.

quasi sun
#

and what if hard setting it to 1000 arbitrarily introduces a security hole because user 1000 has administrative rights? i mean what you are doing is something, but in the end I don't think its the right something, security wise.

#

the project otherwise, i love, i just think this is a misguided security cludge

remote bison
scenic iris
#

Docker container does not works like that you should read some documentation on how permissions works, you can manage the issue you mention
https://docs.docker.com/engine/security/userns-remap/

The remapping itself is handled by two files: /etc/subuid and /etc/subgid. Each file works the same, but one is concerned with the user ID range, and the other with the group ID range. Consider the following entry in /etc/subuid:

testuser:231072:65536

This means that testuser is assigned a subordinate user ID range of 231072 and the next 65536 integers in sequence. UID 231072 is mapped within the namespace (within the container, in this case) as UID 0 (root). UID 231073 is mapped as UID 1, and so forth. If a process attempts to escalate privilege outside of the namespace, the process is running as an unprivileged high-number UID on the host, which does not even map to a real user. This means the process has no privileges on the host system at all.

owner/group restrictions placed on it by docker.
Docker respect the owner/group placed on it, it just don't chown file and also it could be 2000 or 60000 we don't really care that's not a matter

#

And it's not a bug, just linuxserver not doing rootless in the right way. I think linuxserver will still maintain an image so you can wait it if you prefer there.

quasi sun
#

fair enough, thanks for the information. i just dove in a bit deeper and appreciate the information.

vale stratus
#

I’m an Overseerr user who recently upgraded to Radarr v6. While organizing titles in Radarr, I accidentally deleted one of Overseerr’s auto-generated per-user tags (“# – [user]”). Now, Overseerr requests from that user fail because Radarr v6 rejects Overseerr’s attempt to recreate the tag (due to the new label-validation rules). My other Overseerr-generated tags still work fine in both Radarr and Sonarr.

As I prepare for the future move from Overseerr to Seerr, is there any way to manually recreate that missing tag in Radarr so that Overseerr can resume sending requests normally in the meantime? Or how to take the spaces out of the user tag that Overseerr submits to Radarr?

I just donated USD to Overseer last week (before I knew about this merge), I hope that makes it to you guys?

west canyon
vale stratus
#

...or is it literally just "docker pull seerr:develop"

twin escarp
spiral moth
#

hi, I tried pulling latest image of seerr/seerr"develop and receiving this error: ```Node.js v22.20.0

seerr@0.1.0 start

NODE_ENV=production node dist/index.js

2025-12-01T23:09:39.625Z [info]: Commit Tag: c5fc31c35246ed4df8407b1ce4d3a8c4cd023fc4

2025-12-01T23:09:42.027Z [info]: Starting Seerr version develop-c5fc31c35246ed4df8407b1ce4d3a8c4cd023fc4

node:events:497

  throw er; // Unhandled 'error' event

  ^

Error: EACCES: permission denied, open '/app/config/logs/seerr-2025-12-01.log'

Emitted 'error' event at:

at WriteStream.<anonymous> (/app/node_modules/.pnpm/file-stream-rotator@0.6.1/node_modules/file-stream-rotator/FileStreamRotator.js:697:15)

at WriteStream.emit (node:events:519:28)

at emitErrorNT (node:internal/streams/destroy:170:8)

at emitErrorCloseNT (node:internal/streams/destroy:129:3)

at process.processTicksAndRejections (node:internal/process/task_queues:90:21) {

errno: -13,

code: 'EACCES',

syscall: 'open',

path: '/app/config/logs/seerr-2025-12-01.log'```

#

any ideas? Ty

west canyon
#

#seerr-beta message

spiral moth
#

I tried to do that command

#

but wondering if it does not work on docker desktop

#

its giving me this error:

# 
chown : The term 'chown' is not recognized as the name of a cmdlet, function, script file, or operable program. Check
the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ chown -R
+ ~~~~~
    + CategoryInfo          : ObjectNotFound: (chown:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException```
fast plover
#

This is because you are trying to execute a Linux command on a Windows machine chown does not exist in in PowerShell.