Skip to content

hotio/overseerr

GitHub
docker.io / ghcr.io
Overseerr

00

Starting the container

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

version: "3.7"

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

Tags

Tag Description Version Commit SHA Commit Message Last Updated Age

Tags

The above table reflects the current state of the Git repository. The docker repository is mainly in sync, unless builds fail or commits are pushed for which no builds are started (usually indicated with [skip ci] in the commit message). You can click on the tag's name to go to its corresponding branch on GitHub, clicking the commit sha brings you to the git diff of that commit.

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.

Caching images

If you want to cache the image files, you'll have to add an additional volume and make sure that the permissions are correct on the host system.

  -v /<host_folder_images_cache>:/app/.next/cache/images

  volumes:
    - /<host_folder_images_cache>:/app/.next/cache/images