ghcr.io/seerr-team/seerr:latest - manifest unknown

[wild jackal]

Hi guys, whats the deal? Tried to migrate from Overseerr and I get 'Error response from daemon: manifest unknown' when docker tries to pull the image.
checked and double checked I haven't made a mistake but nope...

Ive searched and dont see any mentions of this issue here which seems strange I'd be hitting it..

Thanks in advance!

[empty sigil]

Might wanna triple check that: #seerr-beta message

[gleaming hull]

latest isn't a valid tag

[wild jackal]

Ah, it’s what’s suggested in the migration doc - https://github.com/seerr-team/seerr/blob/develop/docs/migration-guide.mdx

so I should use what? Develop? Should I perhaps wait and use jellyseerr until this is out of beta?
All a bit confusing since there are reddit posts suggesting seerr is the one to use and the git makes it look like it’s all up and ready.

[ornate cedar]

The docs are up to date, but Seerr isn't released yet, which is why it mentions a "wrong" image tag.
Unless you want to try the beta, you should keep using Jellyseerr.

[solar spindle]

Wdym Git makes it look like its all up and ready?

[wild jackal]

Did you look at the migration doc I linked, it’s got instructions and a docker image with latest - not sure there’s anything there said it’s not good to go? Maybe I missed it.

[solar spindle]

Ofc I did. We wrote that. But thats for the https://docs.seerr.dev and you can see its not live there. That migration doc is for beta testing. As stated in #seerr-beta

[solar spindle]

And the file you linked is literally in the "develop" branch as you can see from the url too. "Main" branch is release and you can see that file does not Exist there. If seerr was released, it will be announced and the readme would be complete too

You can use develop tag if you want to beta test

But if not you should be sticking to jellyseerr or overseerr

As stated in #announcements

And #seerr-beta