Skip to content

hotio/overseerr

logo

GitHub Source GitHub Registry Docker Pulls Discord Upstream Website

Starting the container

CLI:

docker run --rm \
    --name overseerr \
    -p 5055:5055 \
    -e PUID=1000 \
    -e PGID=1000 \
    -e UMASK=002 \
    -e TZ="Etc/UTC" \
    -e ARGS="" \
    -e DEBUG="no" \
    -v /<host_folder_config>:/config \
    hotio/overseerr

Compose:

version: "3.7"

services:
  overseerr:
    container_name: overseerr
    image: hotio/overseerr
    ports:
      - "5055:5055"
    environment:
      - PUID=1000
      - PGID=1000
      - UMASK=002
      - TZ=Etc/UTC
      - ARGS
      - DEBUG=no
    volumes:
      - /<host_folder_config>:/config

Tags

Tag Upstream Version Build
release (latest) GitHub releases version build
nightly Every commit to develop branch version build

You can also find tags that reference a commit or version number.

Configuration location

Your overseerr configuration inside the container is stored in /config/app, to migrate from another container, you'd probably have to move your files from /config to /config/app.

Using a secure Plex connection

If you want to keep using secure connections within Plex, but don't want to buy your own domain and keep the connection between Overseerr and Plex inside of their Docker network. Follow the below procedure.

We'll use Google Chrome in this example. Visit https://app.plex.tv and make sure you are logged in. Open Chrome DevTools (usually F12) and open the Console tab, then refresh your browser window. One of the very first lines you will see is [Servers] Initialize server with token, ..., in that message you should see some url that looks like https://10-1-0-100.xxxxxxxxxxxxx.plex.direct:32400. Part of that url can be used in your Overseerr settings, the part 10-1-0-100.xxxxxxxxxxxxx.plex.directis what you'll need to copy/paste, the port is in a seperate input box and enable SSL. You should however give the Plex container a static IP if you don't wanna do this every 5 minutes.

Executing your own scripts

If you have a need to do additional stuff when the container starts or stops, you can mount your script with the volume /docker/host/my-script.sh:/etc/cont-init.d/99-my-script to execute your script on container start or /docker/host/my-script.sh:/etc/cont-finish.d/99-my-script to execute it when the container stops. An example script can be seen below.

#!/usr/bin/with-contenv bash

echo "Hello, this is me, your script."

Troubleshooting a problem

By default all output is redirected to /dev/null, so you won't see anything from the application when using docker logs. Most applications write everything to a log file too. If you do want to see this output with docker logs, you can set DEBUG to yes.