Portainer Templates logo

Portainer Templates

Jellyseerr Jellyseerr

Container

OtherTools

Jellyseer is a free and open source software application for managing requests for your media library.

Image details

Pulls: 37.0M
Architecture: amd64, arm64, arm64/v8
Image size: 409 MB
Latest: 2.7.3
User: fallenbagel
Created: Mar 13, 2022
Updated: 10 months ago
Status: active

Source details

Repo: fallenbagel/jellyseerr
Stars: 12.3k
Forks: 980
Language: TypeScript
License: MIT
Latest: v3.4.1 · 16 days ago
Updated: 12 hours ago
Website: docs.seerr.dev/

Configuration

Type
Container
Platform
linux
Image
fallenbagel/jellyseerr:latest
Ports
5055:5055/tcp
Volumes
/app/config : /portainer/Files/AppData/Config/Jellyseerr
Env vars
PUID=1000PGID=100
Restart
unless-stopped

Template by Qballjos

Standalone Install

Select an install method, to see config/commands for deploying Jellyseerr

Installation method

Install on Portainer

Import all app templates into your Portainer instance, for easy 1-click deploys

  1. Ensure both Docker and Portainer are installed, and up-to-date
  2. Log into your Portainer web UI
  3. Under Settings → App Templates, paste the below URL
  4. Head to Home → App Templates, and the list of apps will show up
  5. Select Jellyseerr, fill in any config options, and hit Deploy

Template Import URL

https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me demo

More install options in our documentation, or see fallenbagel/jellyseerr for app-specific guidance.

Jellyseerr

Discord


Jellyseerr is a free and open source fork of Overseerr for managing requests for your media library. It integrates with your existing services, such as Sonarr, Radarr, and Jellyfin!

Current Features

  • Jellyfin support
  • Easy integration with your existing services. Currently, Jellyseerr supports Sonarr and Radarr.
  • Jellyfin library scan, to keep track of the titles which are already available.
  • Customizable request system, which allows users to request individual seasons or movies in a friendly, easy-to-use interface.
  • Incredibly simple request management UI. Don't dig through the app to simply approve recent requests!
  • Granular permission system.
  • Support for various notification agents.
  • Mobile-friendly design, for when you need to approve requests on the go!

Check out our issue tracker.

Supported Architectures

Jellyseerr image support multiple architectures such as x86-64, arm64 and armv7 (deprecated since release of 2.x.x).
ArchitectureTag
x86-64latest
ARM64latest
ARMv71.9.2 (deprecated)

Version Tags

This image provides two versions that are available via tags. :latest tag provides the latest stable version. :develop are considered under development and caution must be exercised when using them.
TagTag
latestStable Jellyseerr releases
developUnstable Jellyseerr releases

Docker-compose:

Installation through docker compose are as follows:
  • Install docker-compose
  • nano docker-compose.yml
  • Type the following in the docker-compose.yml:
version: '3'
services:
    jellyseerr:
       image: fallenbagel/jellyseerr:latest
       container_name: jellyseerr
       environment:
            - LOG_LEVEL=debug
            - TZ=Asia/Tashkent
       ports:
            - 5055:5055
       volumes:
            - /path/to/appdata/config:/app/config
       restart: unless-stopped
  • docker-compose up -d

Docker CLI

Installation through docker cli can be done by using your terminal and entering the following:
docker run -d \
--name jellyseerr \
-e LOG_LEVEL=debug \
-e TZ=Asia/Tashkent \
-p 5055:5055 \
-v /path/to/appdata/config:/app/config \
--restart unless-stopped \
fallenbagel/jellyseerr:latest

Configuring Dataabase

Check out the Jellyseerr Documentation.

Support

Buy me a Coffee!

If you like jellyseerr and want to help maintain it, please buy me a coffee as it would help me out a lot!
"Buy Me A Coffee"

Serve Jellyseerr on your own domain behind Caddy, Nginx or Traefik. Fill in your domain and copy the result. It's a starting point, some apps need their own base URL or extra headers set too.

Proxying jellyseerr.example.com to http://Jellyseerr:5055

Add this to your Caddyfile

jellyseerr.example.com {
	reverse_proxy http://Jellyseerr:5055
}

Check the logs first

Nine times out of ten the logs tell you exactly what went wrong.

  • In Portainer, go to Containers, click the container, then Logs. Or run docker logs Jellyseerr
  • Exit codes help too: 137 means killed, usually out of memory. 126 or 127 means the command inside the image is broken.

Port already in use

If deployment fails with "Bind for 0.0.0.0:5055 failed: port is already allocated", something else on your server is using that port.

  • Find what's using it: sudo ss -tlnp | grep :5055
  • Stop the other service, or pick a different host port. In 5055:5055 only the left number is yours to change, the right one belongs to the app.

Running but the page won't load

The container is up but nothing appears in your browser.

  • Use your server's real IP: http://your-server-ip:5055. The 0.0.0.0 link Portainer shows isn't a real address.
  • Give it a minute after first deploy, Jellyseerr can take a while to initialise.
  • Make sure your firewall allows the port, e.g. sudo ufw allow 5055

Permission denied on volumes

If the logs show "permission denied", the app can't write to its data folder on the host.

  • Fix the ownership: sudo chown -R 1000:100 /portainer/Files/AppData/Config/Jellyseerr
  • Or set the PUID and PGID variables (defaults 1000:100) to match your own user, found with id $USER

Image won't pull

Test the pull directly on the host: docker pull fallenbagel/jellyseerr:latest

  • "manifest unknown" means the tag no longer exists. This template uses latest, so try pinning a specific version instead.
  • "toomanyrequests" is the Docker Hub rate limit. Log in with docker login to raise it.
  • "no space left on device" means a full disk. Reclaim space with docker system prune

"exec format error"

This means the image was built for a different CPU architecture than your server.

  • This image supports: amd64, arm64, arm64/v8
  • Check yours with uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.

Container keeps restarting

The unless-stopped restart policy relaunches the app after every crash, so the real error can scroll past.

  • Check the logs right after a restart, the last few lines before it died are the useful ones.
  • Get the exit code with docker inspect Jellyseerr --format '{{.State.ExitCode}}'
  • Still stuck? Redeploy once with the restart policy set to no so the failure stays visible.

Raise an issue

Found something which isn't working as it should? Here's how to report it.

A single container

Jellyseerr runs as one container, the simplest kind of app here. Just the one image to pull and nothing else wired up alongside it.

The app image

An image is the app packed up ready to go, everything Jellyseerr needs bundled into one download. This template pulls fallenbagel/jellyseerr:latest, which Docker fetches once (about 409 MB) and then starts your own copy from.

Where the image comes from

Docker pulls its images from registries, public libraries of ready-built apps. Jellyseerr's comes from Docker Hub, published by fallenbagel.

Version tags

The bit after the colon in the image name is the version tag. Here it's latest, which always points at the newest build, so a redeploy can bump you to a newer release without you asking. Newest right now is 2.7.3. Pin a specific tag if you would rather stay on one version.

Which machines it runs on

Every image is built for particular CPU types. This one ships for amd64, arm64, arm64/v8, so it runs on both regular x86 servers and ARM boards like a Raspberry Pi.

Ports

A port is the door the app answers on. A mapping like 5055:5055 means it's reachable on port 5055 of your server, where the left number is yours to change and the right one belongs to the app. It opens:

  • 5055:5055

Volumes

A volume is where Jellyseerr keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:

  • /app/config from /portainer/Files/AppData/Config/Jellyseerr on the host

Environment variables

Environment variables are the settings you hand over when you deploy, things like a password or a timezone. Jellyseerr takes 2 of them, all with defaults you can leave alone or tweak:

  • PUID, defaults to 1000
  • PGID, defaults to 100

Restart policy

The restart policy here is unless-stopped, so Docker restarts Jellyseerr after a crash or reboot, but leaves it off when you stop it on purpose. You can change this on the deploy screen. The choices are no (never restart), on-failure (only after a crash), unless-stopped (restart unless you stop it), and always (bring it back no matter what).

Users and permissions

The PUID and PGID settings tell it which user and group to act as on your host. Point them at your own account (find yours with id $USER) so the files it writes into your mounted folders come out owned by you rather than root.

Networking

Nothing custom is set, so Jellyseerr sits on Docker's default bridge network: its own private space that reaches the outside world only through the ports it publishes.

Container name

Once it's deployed, Portainer names the container Jellyseerr. That's what you'll spot in the containers list and use in commands like docker logs Jellyseerr.

Platform

The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.

Open source license

Jellyseerr is open source, released under the MIT license. In plain terms the code is out in the open, so you're free to run it and change it to fit what you need.

Portainer app templates

Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set Jellyseerr up. Add the template list to Portainer once, then deploying Jellyseerr is a click rather than a wall of config.