Portainer Templates logo

Portainer Templates

PodFetch PodFetch

MediaDownloaders

Sleek, self-hosted podcast manager that automatically downloads new episodes, offers a web UI for listening, and provides a GPodder-compatible sync API for mobile apps like AntennaPod.

Image details

Pulls: 437k
Architectures: amd64, arm64, arm/v7
Image size: 141 MB
Latest: v5.2.2-33a8714a
User: samuel19982
Created: Apr 11, 2023
Updated: 2 days ago
Status: active

Source details

Stars: 490
Forks: 35
Language: Rust
License: Apache-2.0
Updated: 2 days ago

Configuration

Type
Container
Platform
linux
Image
samuel19982/podfetch:latest
Ports
8000:8000/tcp
Volumes
/app/podcasts : /portainer/Files/AppData/PodFetch/podcasts/app/db : /portainer/Files/AppData/PodFetch/db
Env vars
DATABASE_URL=sqlite:///app/db/podcast.dbPOLLING_INTERVAL=300BASIC_AUTH=falseUSERNAME=PASSWORD=GPODDER_INTEGRATION_ENABLED=false
Restart
unless-stopped

Notes

To use the GPodder sync API, set BASIC_AUTH=true together with USERNAME and PASSWORD, and set GPODDER_INTEGRATION_ENABLED=true. Documentation: https://samtv12345.github.io/PodFetch/

Installation

  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 the app you wish to deploy, fill in any config options, and hit Deploy

Template Import URL

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

docker run -d --name podfetch \
  -p 8000:8000/tcp \
  -e 'DATABASE_URL=sqlite:///app/db/podcast.db' \
  -e 'POLLING_INTERVAL=300' \
  -e 'BASIC_AUTH=false' \
  -e 'USERNAME=' \
  -e 'PASSWORD=' \
  -e 'GPODDER_INTEGRATION_ENABLED=false' \
  -v /portainer/Files/AppData/PodFetch/podcasts:/app/podcasts \
  -v /portainer/Files/AppData/PodFetch/db:/app/db \
  --restart=unless-stopped \
  samuel19982/podfetch:latest

Save this file as compose.yaml and run docker compose up -d
Use this only as a guide.

services:
  podfetch:
    image: samuel19982/podfetch:latest
    ports:
      - 8000:8000/tcp
    volumes:
      - /portainer/Files/AppData/PodFetch/podcasts:/app/podcasts
      - /portainer/Files/AppData/PodFetch/db:/app/db
    environment:
      DATABASE_URL: sqlite:///app/db/podcast.db
      POLLING_INTERVAL: '300'
      BASIC_AUTH: 'false'
      USERNAME: ''
      PASSWORD: ''
      GPODDER_INTEGRATION_ENABLED: 'false'
    restart: unless-stopped

Save this file as podfetch-stack.yml, then from a manager node, run docker stack deploy -c podfetch-stack.yml podfetch

version: '3.8'
services:
  podfetch:
    image: samuel19982/podfetch:latest
    ports:
      - 8000:8000/tcp
    volumes:
      - /portainer/Files/AppData/PodFetch/podcasts:/app/podcasts
      - /portainer/Files/AppData/PodFetch/db:/app/db
    environment:
      DATABASE_URL: sqlite:///app/db/podcast.db
      POLLING_INTERVAL: '300'
      BASIC_AUTH: 'false'
      USERNAME: ''
      PASSWORD: ''
      GPODDER_INTEGRATION_ENABLED: 'false'
    deploy:
      restart_policy:
        condition: any

Save each file below into a folder, then run kubectl apply -f .
Written for k3s, but works on any cluster: bind mounts use hostPath, named volumes get a persistent volume claim, and ports are exposed via a LoadBalancer service.

podfetch-deployment.yaml

apiVersion: apps/v1
kind: Deployment
metadata:
  name: podfetch
  labels:
    app: podfetch
spec:
  replicas: 1
  selector:
    matchLabels:
      app: podfetch
  template:
    metadata:
      labels:
        app: podfetch
    spec:
      containers:
        - name: podfetch
          image: samuel19982/podfetch:latest
          env:
            - name: DATABASE_URL
              value: sqlite:///app/db/podcast.db
            - name: POLLING_INTERVAL
              value: '300'
            - name: BASIC_AUTH
              value: 'false'
            - name: USERNAME
              value: ''
            - name: PASSWORD
              value: ''
            - name: GPODDER_INTEGRATION_ENABLED
              value: 'false'
          ports:
            - containerPort: 8000
              protocol: TCP
          volumeMounts:
            - name: podfetch-data-0
              mountPath: /app/podcasts
            - name: podfetch-data-1
              mountPath: /app/db
      volumes:
        - name: podfetch-data-0
          hostPath:
            path: /portainer/Files/AppData/PodFetch/podcasts
        - name: podfetch-data-1
          hostPath:
            path: /portainer/Files/AppData/PodFetch/db

podfetch-service.yaml

apiVersion: v1
kind: Service
metadata:
  name: podfetch
spec:
  type: LoadBalancer
  selector:
    app: podfetch
  ports:
    - name: 8000-tcp
      port: 8000
      targetPort: 8000
      protocol: TCP

Save this file as ~/.config/containers/systemd/podfetch.container

[Unit]
Description=PodFetch

[Container]
Image=samuel19982/podfetch:latest
ContainerName=podfetch
PublishPort=8000:8000/tcp
Environment=DATABASE_URL=sqlite:///app/db/podcast.db
Environment=POLLING_INTERVAL=300
Environment=BASIC_AUTH=false
Environment=USERNAME=
Environment=PASSWORD=
Environment=GPODDER_INTEGRATION_ENABLED=false
Volume=/portainer/Files/AppData/PodFetch/podcasts:/app/podcasts
Volume=/portainer/Files/AppData/PodFetch/db:/app/db

[Service]
Restart=always

[Install]
WantedBy=default.target

Then reload systemd and start the service:

systemctl --user daemon-reload
systemctl --user start podfetch

For a system-wide service, use /etc/containers/systemd/ and drop --user.

For more installation options, see the Documentation in our GitHub repo

For app-specific guidance, check PodFetch's own repo at samtv12345/PodFetch

version: '3'
services:
  podfetch:
    image: samuel19982/podfetch:latest
    ports:
      - "80:8000"
    volumes:
      - podgrab-podcasts:/app/podcasts
      - podgrab-db:/app/db
    environment:
      - POLLING_INTERVAL=60
      - SERVER_URL=http://localhost:80
      - DATABASE_URL=sqlite:///app/db/podcast.db

volumes:
    podgrab-podcasts:
    podgrab-db:

Serve PodFetch 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 podfetch.example.com to http://podfetch:8000

Add this to your Caddyfile

podfetch.example.com {
	reverse_proxy http://podfetch: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 podfetch
  • 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:8000 failed: port is already allocated", something else on your server is using that port.

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

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/PodFetch/podcasts (and the same for the other mapped folders)

Image won't pull

Test the pull directly on the host: docker pull samuel19982/podfetch: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, arm/v7
  • 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 podfetch --format '{{.State.ExitCode}}'
  • Still stuck? Redeploy once with the restart policy set to no so the failure stays visible.

Required settings are blank

USERNAME, PASSWORD have no default value, and podfetch may crash or misbehave if left empty.

  • Fill them in on the deploy screen before hitting deploy.

Raise an issue

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

Similar apps