Portainer Templates logo

Portainer Templates

Filepizza Filepizza

Stack

Downloaders

Peer-to-peer file transfers in your browser

Configuration

Type
Compose
Platform
linux
Source
Repo

Template by xneo1·Source

Services

filepizza

Configuration

Image
kern/filepizza:latest
Ports
3333:3333
Env vars
PORT=3333EXTRA_ICE_SERVERS=turn:localhost:3478WEBTORRENT_TRACKERS=ws://localhost:28000
Restart
always
Build
[object Object]

Image details

Pulls: 786k
User: kern
Created: Apr 11, 2016
Updated: 6 months ago
Status: active

coturn

Configuration

Image
instrumentisto/coturn:latest
Ports
3478:3478

Image details

Pulls: 24.4M
User: instrumentisto
Created: May 18, 2018
Updated: 5 years ago
Status: active

bittorrent-tracker

Configuration

Image
henkel/bittorrent-tracker:latest
Command
npx,bittorrent-tracker,--http-hostname,0.0.0.0,--ws
Ports
28000:8000

Standalone Install

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

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 Filepizza, 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:
  filepizza:
    image: kern/filepizza:latest
    restart: always
    build:
      context: .
    ports:
      - 3333:3333
    environment:
      - PORT=3333
      - EXTRA_ICE_SERVERS=turn:localhost:3478
      - WEBTORRENT_TRACKERS=ws://localhost:28000
  coturn:
    image: instrumentisto/coturn:latest
    network_mode: host
    ports:
      - 3478:3478
  bittorrent-tracker:
    image: henkel/bittorrent-tracker:latest
    command: ["npx", "bittorrent-tracker", "--http-hostname", "0.0.0.0", "--ws"]
    ports:
    - 28000:8000

Or deploy it directly from the source:

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

More install options in our documentation.

Container Documentation

coturn Documentation

[Closed] Coturn TURN server Docker image

Serve Filepizza 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 filepizza.example.com to http://bittorrent-tracker:8000

Add this to your Caddyfile

filepizza.example.com {
	reverse_proxy http://bittorrent-tracker:8000
}

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:3333 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:28000. The 0.0.0.0 link Portainer shows isn't a real address.
  • Give it a minute after first deploy, filepizza can take a while to initialise.
  • Make sure your firewall allows the port, e.g. sudo ufw allow 28000

Image won't pull

Test the pull directly on the host: docker pull kern/filepizza: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 always 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

Filepizza is a Compose stack, a set of containers (3 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 3 containers that run side by side. Here's each one, with the image it runs and anything it waits for first:

  • filepizza runs kern/filepizza:latest
  • coturn runs instrumentisto/coturn:latest
  • bittorrent-tracker runs henkel/bittorrent-tracker:latest

Ports

A port is the door the app answers on. A mapping like 3333:3333 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:28000 in a browser. It opens:

  • 3333:3333
  • 3478:3478
  • 28000:8000, likely the web interface

Environment variables

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

  • PORT, defaults to 3333
  • EXTRA_ICE_SERVERS, defaults to turn:localhost:3478
  • WEBTORRENT_TRACKERS, defaults to ws://localhost:28000

Restart policy

The restart policy here is always, so Docker brings Filepizza back up after a crash and again when the server reboots. Good for anything you want running around the clock. 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 filepizza) 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 Filepizza up. Add the template list to Portainer once, then deploying Filepizza is a click rather than a wall of config.