25
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 23 Feb 2026
25 points (100.0% liked)
Selfhosted
58324 readers
686 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 2 years ago
MODERATORS
Here is a migration guide from the devs: https://docs.seerr.dev/migration-guide
How did you install Overseerr in CasaOS?
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.
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)
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.
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 know my way around it's basics if it makes it easier.
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.
ok great thank you!