Repository navigation
[FEAT] Migration to Seerr #56
Description
Activity
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
I also came here wondering about this. Is this container going to deprecated or updated?
Thanks for all your great containers!
I'm also interested if you plan to migrate to the new seerr.
For anyone wondering about migration from this linuxserver image back to the official image (as suggested by the deprecation notice sent above), the migration was essentially seamless (other than than my own user errors haha) by following seerr's own migration guide.
In other words, I had no issues migrating from linuxserver to official by running with the docker compose stack.
Somethings to watch out for when going through the official migration doc :
- the
volumespath in linuxserver image is/config, while in the official image, it is/app/config - the notice about the container running with the user of PID
1000also applies here, I had permissions issues until I ran essentially the suggested commanddocker run --rm -v /path/to/appdata/config:/data alpine chown -R 1000:1000 /data - the
TZenv var does not work anymore, haven't looked into fixing that as it isn't too big of a deal (essentially only TZ issue is in the docker logs, seerr's webui still display user timezones) - linuxserver compose stack did not have the healthcheck, while the official one does - I added it myself for more checks, why not, but optional
But yeah, essentially seamless, but got caught off guards with
1..Compose stack that I now run
seerr: image: ghcr.io/seerr-team/seerr:latest container_name: seerr init: true environment: - PUID=${PUID:-1000} - PGID=${PGID:-100} - TZ=Canada/Eastern - PORT=5055 #optional ports: - 5055:5055 volumes: - ${CONFIG_FLD}/seerr:/app/config healthcheck: test: wget --no-verbose --tries=1 --spider http://localhost:5055/api/v1/status || exit 1 start_period: 20s timeout: 3s interval: 15s retries: 3 labels: - com.centurylinklabs.watchtower.enable=true restart: unless-stoppedThe
PUID,PGIDandTZare no longer being respected, but ah wellReacted by spcrepeau, tr4cks, Lord Drakath and Tyler BrockettReacted by Mickael V- the
I also followed the migration guide for Seerr and my migration was even easier than V-ed.
I back up first.I am using unraid.
Stopped my overseerr instance.
Found the official docker on unraids app centre.
Installed with my docker vlan and my static IP address instead of bridged.
Changed the config and logs folder to my current overseerr location.
Proceeded with install.
Everything worked, all settings migrated automatically.Reacted by Guillaume MarcouxI also followed the migration guide for Seerr and my migration was even easier than V-ed. I back up first.
I am using unraid. Stopped my overseerr instance. Found the official docker on unraids app centre. Installed with my docker vlan and my static IP address instead of bridged. Changed the config and logs folder to my current overseerr location. Proceeded with install. Everything worked, all settings migrated automatically.
I did the same. All is working for me now as well.
For anyone seeing certificate issues for radarr/sonarr when using their own certificate authority..
Overseer used os certificates installed to/etc/ssl/certs/, but Seer does not. I build my own image which I had to update for seer:FROM ghcr.io/seerr-team/seerr:latest COPY internal-ca.crt /usr/local/share/ca-certificates/internal-ca.crt USER root RUN apk update; \ apk add --no-cache ca-certificates; \ update-ca-certificates -v; \ USER 1000:1000
Then in my docker-compose for seer, I also have to set the environment
NODE_EXTRA_CA_CERTS=/etc/ssl/certs/ca-certificates.crt.All works now.
I switched in the mean time using the migration guide.
Brought down my existing container
docker compose downI used the docker compose example and created a new docker-compose.yml
seerr: image: ghcr.io/seerr-team/seerr:latest init: true container_name: seerr environment: - LOG_LEVEL=debug - TZ=Pacific/Auckland - PORT=5055 #optional ports: - 5055:5055 networks: - networkname volumes: - ./config:/app/config healthcheck: test: wget --no-verbose --tries=1 --spider http://localhost:5055/api/v1/status || exit 1 start_period: 20s timeout: 3s interval: 15s retries: 3 restart: unless-stopped networks: networkname: external: trueUpdated the perms on the config directory
sudo chown -R 1000:1000 configAnd then brought up the new container
docker compose up -d
Is this a new feature request?
Wanted change
Is there a plan to release a linuxserver/seerr image now that the seerr app is released in v3.0?
Reason for change
The new unified seerr app is released and overseerr will not be maintained any more. I think we all like the stability and common features of the linuxserver versions. Also, I'd be curious if there are any gotchas in the initial migration when coming from linuxserver version instead of their default image.
Proposed code change
point underlying image to the new seerr-team/seerr image.