this post was submitted on 23 Feb 2026
8 points (83.3% liked)

Selfhosted

56821 readers
881 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

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?

top 6 comments
sorted by: hot top controversial new old
[–] fixmycode@feddit.cl 1 points 40 minutes ago

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.

[–] bigb@lemmy.blahaj.zone 6 points 2 hours ago* (last edited 2 hours ago) (2 children)

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.

[–] flork@lemy.lol 1 points 1 hour ago* (last edited 1 hour ago)

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.

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.

[–] slazer2au@lemmy.world 1 points 1 hour ago (1 children)

Change your compose file image to the new one? That is what I did.

***
services:
  seerr:
    image: ghcr.io/seerr-team/seerr:latest
[–] flork@lemy.lol 1 points 1 hour ago

CasaOS doesn't have a way to do that, how can I do that in Portainer?