Portainer Templates logo

Portainer Templates

Invidious Invidious

Stack

Multimedia

Invidious is an open source alternative front-end to YouTube.

Configuration

Type
Compose
Platform
linux
Source
Repo

Template by xneo1·Source

Services

invidious

Configuration

Image
quay.io/invidious/invidious:latest
Ports
3333:3000
Env vars
INVIDIOUS_CONFIG=db: dbname: invidious user: oneusr password: onepwd host: invidious-db port: 5432 check_tables: true # external_port: # domain: # https_only: false # statistics_enabled: false hmac_key: "CHANGE_ME!!"
Restart
unless-stopped

invidious-db

Configuration

Image
docker.io/library/postgres:14
Volumes
/var/lib/postgresql/data : /portainer/Files/AppData/Config/invidious/postgresdata/config/sql : /portainer/Files/AppData/Config/invidious/postgresdata/config/sql/docker-entrypoint-initdb.d/init-invidious-db.sh : /portainer/Files/AppData/Config/invidious/postgresdata/init-invidious-db.sh
Env vars
POSTGRES_DB=invidiousPOSTGRES_USER=theuserPOSTGRES_PASSWORD=thepwd
Restart
unless-stopped

Image details

Pulls: 11.2B
User: stackbrew
Created: Jun 05, 2014
Updated: 1 hour ago
Status: active

Standalone Install

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

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 Invidious, fill in any config options, and hit Deploy

Template Import URL

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

The compose file this template deploys, straight from its repo:

services:

  invidious:
    image: quay.io/invidious/invidious:latest
    # image: quay.io/invidious/invidious:latest-arm64 # ARM64/AArch64 devices
    restart: unless-stopped
    ports:
      - 3333:3000
    environment:
      # Please read the following file for a comprehensive list of all available
      # configuration options and their associated syntax:
      # https://github.com/iv-org/invidious/blob/master/config/config.example.yml
      INVIDIOUS_CONFIG: |
        db:
          dbname: invidious
          user: oneusr
          password: onepwd
          host: invidious-db
          port: 5432
        check_tables: true
        # external_port:
        # domain:
        # https_only: false
        # statistics_enabled: false
        hmac_key: "CHANGE_ME!!"
    healthcheck:
      test: wget -nv --tries=1 --spider http://127.0.0.1:3000/api/v1/trending || exit 1
      interval: 30s
      timeout: 5s
      retries: 2
    logging:
      options:
        max-size: "1G"
        max-file: "4"
    depends_on:
      - invidious-db

  invidious-db:
    image: docker.io/library/postgres:14
    restart: unless-stopped
    volumes:
      - /portainer/Files/AppData/Config/invidious/postgresdata:/var/lib/postgresql/data
      - /portainer/Files/AppData/Config/invidious/postgresdata/config/sql:/config/sql
      - /portainer/Files/AppData/Config/invidious/postgresdata/init-invidious-db.sh:/docker-entrypoint-initdb.d/init-invidious-db.sh
    environment:
      POSTGRES_DB: invidious
      POSTGRES_USER: theuser
      POSTGRES_PASSWORD: thepwd
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U $$POSTGRES_USER -d $$POSTGRES_DB"]

volumes:
  postgresdata:

Or deploy it directly from the source:

git clone https://github.com/xneo1/portainer_templates
cd portainer_templates
docker compose -f Template/Stack/invidious.yml up -d

More install options in our documentation.

Container Documentation

invidious-db Documentation

The PostgreSQL object-relational database system provides reliability and data integrity.

Serve Invidious 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 invidious.example.com to http://invidious:3000

Add this to your Caddyfile

invidious.example.com {
	reverse_proxy http://invidious:3000
}

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 <container>
  • 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:3333 failed: port is already allocated", something else on your server is using that port.

  • Find what's using it: sudo ss -tlnp | grep :3333
  • Stop the other service, or pick a different host port. In 3333:3000 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:3333. The 0.0.0.0 link Portainer shows isn't a real address.
  • Give it a minute after first deploy, Invidious can take a while to initialise.
  • Make sure your firewall allows the port, e.g. sudo ufw allow 3333

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:1000 /portainer/Files/AppData/Config/invidious/postgresdata (and the same for the other mapped folders)

Image won't pull

Test the pull directly on the host: docker pull quay.io/invidious/invidious: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.

  • 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 <container> --format '{{.State.ExitCode}}'
  • Still stuck? Redeploy once with the restart policy set to no so the failure stays visible.

Stack won't deploy

Compose stacks fail fast on small mistakes, and Portainer shows the reason just above the editor.

  • YAML only accepts spaces for indentation, a single tab breaks the whole file.

Raise an issue

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

A Compose stack

Invidious is a Compose stack, a set of containers (2 of them) defined in one file and brought up together by Portainer, then started and stopped as a single app.

The services

This stack is built from 2 containers that run side by side. Here's each one, with the image it runs and anything it waits for first:

  • invidious runs quay.io/invidious/invidious:latest, starts after invidious-db
  • invidious-db runs docker.io/library/postgres:14

Ports

A port is the door the app answers on. A mapping like 3333:3000 means it's reachable on port 3333 of your server, where the left number is yours to change and the right one belongs to the app. Once it's running, open http://your-server-ip:3333 in a browser. It opens:

  • 3333:3000, likely the web interface

Volumes

A volume is where Invidious 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:

  • /var/lib/postgresql/data from /portainer/Files/AppData/Config/invidious/postgresdata on the host
  • /config/sql from /portainer/Files/AppData/Config/invidious/postgresdata/config/sql on the host
  • /docker-entrypoint-initdb.d/init-invidious-db.sh from /portainer/Files/AppData/Config/invidious/postgresdata/init-invidious-db.sh on the host

Environment variables

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

  • INVIDIOUS_CONFIG, defaults to db: dbname: invidious user: oneusr password: onepwd host: invidious-db port: 5432 check_tables: true # external_port: # domain: # https_only: false # statistics_enabled: false hmac_key: "CHANGE_ME!!"
  • POSTGRES_DB, defaults to invidious
  • POSTGRES_USER, defaults to theuser
  • POSTGRES_PASSWORD, defaults to thepwd

Restart policy

The restart policy here is unless-stopped, so Docker restarts Invidious 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).

Networking

Portainer puts these services on one shared private network, so they can find each other by name (like invidious) while only the ports above are open to you.

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.

Portainer app templates

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