MeTube with Docker Compose

What MeTube needs

Only figures MeTube's own documentation publishes, each linked to the page it is on. Where the project gives no number, this page does not invent one.

On top of this, Caddy (the reverse proxy in the file) is a single small container.

Which hardware MeTube has images for

Read from each image's manifest list in its registry (anonymous, read-only) when this page was built. An app counts for a CPU only if every one of its images lists it.

• x86-64 PC or NAS (linux/amd64): every image has a build.
• Raspberry Pi 4/5, 64-bit OS (linux/arm64): every image has a build.
• Raspberry Pi 3 or Zero 2 W, 32-bit OS (linux/arm/v7): no image for metube. No image for this hardware; the builder leaves the app out.

A manifest says an image exists for a CPU, not how well MeTube runs on it: a build for arm64 or arm/v7 can still be too slow or need more memory than the board has. The RAM and disk MeTube publishes are in the table above and, for a whole set of apps against a Raspberry Pi, on Will it run on my machine?. A tag like latest can move to a new digest after the date checked.

docker-compose.yml

This is exactly what the builder writes for MeTube alone on example.org: the official definition with its published ports removed and Caddy added in front.

# docker-compose.yml built at dankhost.com for: MeTube
# Each app block is its official compose definition. Only the names were prefixed with
# the app slug (services, containers, volumes, bind folders, .env variables) so any set of
# apps can share one file; other differences are listed under "Changed:" in each block.
# Only Caddy publishes ports. Secrets live in .env next to this file.

services:
  # ---- Caddy: the one reverse proxy, HTTPS certificates from Let's Encrypt ----
  # Source: https://caddyserver.com/docs/running (checked 2026-09-23)
  # Source: https://github.com/dani-garcia/vaultwarden/wiki/Using-Docker-Compose (checked 2026-09-23)
  # Caddyfile goes in ./caddy/Caddyfile. Fixed address 172.30.0.2 so apps can trust it exactly.
  caddy:
    image: "caddy:2"
    container_name: "caddy"
    restart: "unless-stopped"
    ports:
      - "80:80"
      - "443:443"
      - "443:443/udp"
    volumes:
      - "./caddy:/etc/caddy"
      - "caddy-data:/data"
      - "caddy-config:/config"
    networks:
      proxy:
        ipv4_address: "172.30.0.2"

  # ---- MeTube (metube.example.org) ----
  # Source: https://github.com/alexta69/metube/blob/master/README.md (checked 2026-10-08)
  # Source: https://github.com/alexta69/metube/wiki/Reverse-proxy-configurations (checked 2026-10-08)
  # Changed: Removed the documented '8081:8081' port and container_name; Caddy reaches metube:8081 on the proxy network.
  #          The download folder, /path/to/downloads in the README, is ./downloads next to this file.
  metube:
    image: "ghcr.io/alexta69/metube"
    container_name: "metube"
    restart: "unless-stopped"
    volumes:
      - "./metube/downloads:/downloads"
    networks:
      proxy: {}

networks:
  # Pinned so the trusted-proxy address given to each app (172.30.0.2) is exact.
  # If "docker compose up" reports "Pool overlaps", change 172.30.0 here, in Caddy's
  # ipv4_address and in every trusted-proxy value to a free 172.x.0 range.
  proxy:
    ipam:
      config:
        - subnet: "172.30.0.0/24"
          ip_range: "172.30.0.128/25"
          gateway: "172.30.0.1"

volumes:
  caddy-data:
  caddy-config:

Caddyfile save as caddy/Caddyfile

Caddy gets and renews the HTTPS certificate for metube.example.org by itself once the DNS record points at your server and ports 80 and 443 reach it.

# Caddyfile built at dankhost.com. Save it as ./caddy/Caddyfile next to docker-compose.yml.
# Caddy gets and renews a Let's Encrypt certificate for each name below by itself,
# once the DNS records point at this server and ports 80 and 443 reach it.

# MeTube
metube.example.org {
	reverse_proxy metube:8081
}

Already running nginx, Nginx Proxy Manager, Caddy or Traefik? The reverse-proxy settings MeTube needs, for all four, each cited to MeTube's own docs.

.env

MeTube needs no secret here; the builder adds nothing you have to fill in by hand.

# .env for MeTube, from dankhost.com/app/metube/. Nothing here is secret.
# Keep this file private (chmod 600).
# None of the chosen apps needs a variable here.

Changes from the official file

Besides prefixing every service, container, volume, folder and variable with metube (so any set of apps can share one file), these are all the differences from what the project documents:

• Removed the documented '8081:8081' port and container_name; Caddy reaches metube:8081 on the proxy network.
• The download folder, /path/to/downloads in the README, is ./downloads next to this file.

Notes for MeTube behind the proxy

• MeTube has no login. Anyone who can open https://metube.example.org can make your server download anything, so do not leave it open on the internet: put a password in front of it on the proxy (the wiki's reverse-proxy page shows how to add authentication) or reach it only from your home network or a VPN.
• Downloads land in ./metube/downloads. The queue, history, subscriptions and uploaded cookies are kept in its .metube folder (STATE_DIR, /downloads/.metube by default).
• MeTube runs as PUID/PGID 1000 and makes that user the owner of the download folder at start (CHOWN_DIRS=true). Set PUID and PGID under metube's environment if the files should belong to someone else.
• The image has no tag, which is latest. The README: a new image is published for every yt-dlp stable release, and sites change constantly, so pull often.

Back it up

MeTube publishes no backup procedure. Everything it keeps is in the download folder: your files, and the queue, history and subscriptions in its .metube folder.

Below is the BACKUP.md the builder writes next to the compose file above: which of its folders and volumes hold data, what to copy with which container stopped, and a restore check. Pick more apps in the builder and it covers them all in one file.

# BACKUP.md built at dankhost.com for: MeTube

What to copy from the docker-compose.yml built with this file, the database dump each project documents (rewritten for the service names in that file), what to copy with which container stopped, and how to check the result. Run every command in the folder that holds docker-compose.yml.

The folders are owned by the containers' users: put sudo in front of tar if it says "Permission denied". Named volumes live under /var/lib/docker/volumes, not next to the compose file, so they are copied through a throwaway ubuntu container (Docker's documented --volumes-from method). tar makes a full copy each run; for large folders an incremental tool (restic, borg, rsync) saves time and space.

Never run "docker compose down -v" on this file: it deletes the named volumes of every app in it.

## Before you start

    BACKUP=/mnt/backup/selfhost   # change this: a disk or machine other than this server's system disk
    mkdir -p "$BACKUP"

## Every time: the three stack files

    tar czf "$BACKUP/stack-files.tar.gz" docker-compose.yml .env caddy

.env holds the database passwords and secret keys the apps were set up with; keep this archive as private as the data.

## Caddy (the reverse proxy)

Caddy's docs: 'The data directory must not be treated as a cache.' It holds the TLS certificates and their private keys; without it Caddy has to ask Let's Encrypt for every certificate again.

- caddy-data (named volume, /data in caddy)
  BACK UP: TLS certificates, private keys, OCSP staples.
- caddy-config (named volume, /config in caddy)
  SKIP: the last active configuration, kept for 'caddy run --resume', which this setup does not use: it starts from the Caddyfile.
- ./caddy (/etc/caddy in caddy)
  IN stack-files.tar.gz: the Caddyfile, copied with the stack files above.

Copy (Caddy keeps serving while you copy):

    docker run --rm --volumes-from caddy -v "$BACKUP":/backup ubuntu tar cvf /backup/caddy-data.tar /data

Restore check:

    tar tf "$BACKUP/caddy-data.tar" > /dev/null && echo OK
    docker run --rm --volumes-from caddy -v "$BACKUP":/backup ubuntu bash -c "cd /data && tar xvf /backup/caddy-data.tar --strip 1"

Sources:
- Caddy docs: Conventions, Data directory: https://caddyserver.com/docs/conventions#data-directory (checked 2026-09-24)
- Docker docs: Volumes, Back up, restore, or migrate data volumes: https://docs.docker.com/engine/storage/volumes/#back-up-restore-or-migrate-data-volumes (checked 2026-09-24)

## MeTube

MeTube publishes no backup procedure. Everything it keeps is in the download folder: your files, and the queue, history and subscriptions in its .metube folder.

What this compose mounts:
- ./metube/downloads (/downloads in metube)
  BACK UP: the downloaded videos and audio, and .metube/ with the queue, history, subscriptions and uploaded cookies.

1. Copy (MeTube keeps running):
   Finished downloads do not change; a download still running is simply copied half-way and can be fetched again.

    tar czf "$BACKUP/metube-downloads.tar.gz" ./metube/downloads

Restore check:

    tar tzf "$BACKUP/metube-downloads.tar.gz" > /dev/null && echo OK

Put a copy back (with MeTube stopped):

    tar xzf "$BACKUP/metube-downloads.tar.gz"   # recreates ./metube/downloads; move the old folder aside first

Put ./metube/downloads back and run docker compose up -d.

Sources:
- MeTube README (Docker Compose, environment variables, multi-arch images): https://github.com/alexta69/metube/blob/master/README.md (checked 2026-10-08)
- Docker docs: Volumes, Back up, restore, or migrate data volumes: https://docs.docker.com/engine/storage/volumes/#back-up-restore-or-migrate-data-volumes (checked 2026-10-08)

Update it

What docker compose pull does depends only on how each image line in the compose file above is tagged. For MeTube as this page writes it:

What MeTube's docs say about updating

MeTube's README: a new image is published automatically for every yt-dlp stable release, "so keep your container updated". With this compose file:

docker compose pull
docker compose up -d

• Sites break when yt-dlp falls behind, so a download that suddenly fails is often fixed by updating.

Source: MeTube README (Docker Compose, environment variables, multi-arch images) checked 2026-10-08

The steps

1. Back up first, as in Back it up above. An update can migrate MeTube's data on its first start; the copy is the way back.
2. Download the new images. Running containers are not touched yet:

   docker compose pull

3. Recreate the containers whose image changed. Volumes and bind-mounted folders stay as they are:

   docker compose up -d

4. Watch MeTube start (Ctrl+C stops following the log, not the app):

   docker compose logs -f metube

5. Optional: remove the old images the pull left without a tag. This covers every stack on the machine, not only this one:

   docker image prune

Docker's reference for these commands: Docker docs: docker compose pull checked 2026-09-30; Docker docs: docker compose up (recreates changed containers, keeps volumes) checked 2026-09-30; Docker docs: docker image prune checked 2026-09-30

Locked out? Reset the admin password

MeTube has no accounts and no login, so there is no password to reset.

The README lists no user or password setting, and its reverse-proxy wiki page adds authentication on the proxy instead. Anyone who can reach the address can use MeTube, so if you want a password, put it on the proxy. Source: MeTube README (Configuration: no user or password setting) read 2026-10-08; MeTube wiki: Reverse proxy configurations (WebSocket for Socket.IO, URL_PREFIX) read 2026-10-08

Sources

Every page below was fetched on the date shown.

• MeTube on GitHub (repository description) checked 2026-10-08 (what it does)
• MeTube README (Docker Compose, environment variables, multi-arch images) checked 2026-10-08 (compose definition and proxy settings, backup plan, update notes)
• MeTube wiki: Reverse proxy configurations (WebSocket for Socket.IO, URL_PREFIX) checked 2026-10-08 (compose definition and proxy settings)
• Caddy docs: Keep Caddy running (Docker Compose section) checked 2026-09-23 (Caddy)
• Vaultwarden wiki: Caddy with HTTP challenge (uses the caddy:2 image) checked 2026-09-23 (Caddy)
• Docker docs: Volumes, Back up, restore, or migrate data volumes checked 2026-10-08 (backup plan)
• Caddy docs: Conventions, Data directory checked 2026-09-24 (backup plan)
• Docker docs: docker compose pull checked 2026-09-30 (update steps)
• Docker docs: docker compose up (recreates changed containers, keeps volumes) checked 2026-09-30 (update steps)
• Docker docs: docker image prune checked 2026-09-30 (update steps)

Add MeTube to the builder All one hundred apps