FreshRSS with Docker Compose
FreshRSS is a self-hosted RSS feed aggregator. It is lightweight, easy to work with, powerful, customizable, and a multi-user application with an anonymous reading mode. In the project's words: FreshRSS README checked 2026-09-23
Runs on: amd64, arm64, arm/v7 from each image's registry manifest, checked 2026-09-25; a CPU counts only if every image has a build for it. Image by image
Add FreshRSS to the builder to use your own domain and combine it with other apps in one file.
What FreshRSS needs
Only figures FreshRSS's own documentation publishes, each linked to the page it is on. Where the project gives no number, this page does not invent one.
| Resource | Minimum | Recommended |
|---|---|---|
| RAM | The project publishes no figure | |
| CPU | The project publishes no figure | |
| No figure; the README asks for a "light server" and says it even works on a Raspberry Pi 1 with response times under a second (tested with 150 feeds and 22k articles). Source: FreshRSS README (Requirements) checked 2026-09-23 | ||
| Disk | The project publishes no figure | |
Which hardware FreshRSS 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.
With SQLite, the default
- 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): every image has a build.
| Service | Image | Platforms in the manifest | Digest | Registry | Checked |
|---|---|---|---|---|---|
freshrss | freshrss/freshrss:latest | amd64, arm/v7, arm64 | sha256:258b8edfc8a76a61f60d2d6a14d8f8d12495d78abf38646a2137612dfa264a21 | registry-1.docker.io | 2026-09-25 |
With PostgreSQL
- 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): every image has a build.
| Service | Image | Platforms in the manifest | Digest | Registry | Checked |
|---|---|---|---|---|---|
freshrss | freshrss/freshrss:latest | amd64, arm/v7, arm64 | sha256:258b8edfc8a76a61f60d2d6a14d8f8d12495d78abf38646a2137612dfa264a21 | registry-1.docker.io | 2026-09-25 |
freshrss-db | postgres:18 | amd64, arm/v5, arm/v7, arm64, 386, ppc64le, riscv64, s390x | sha256:5a5a84b19854a9ffaa54082c166ff4ec27473a361e496e5ea167f298f2da9722 | registry-1.docker.io | 2026-09-25 |
docker-compose.yml
FreshRSS runs on SQLite by default; its repository ships docker-compose-db.yml, a PostgreSQL service to add to the same Compose project. FreshRSS can also change database later: its Backup page backs each user up to SQLite with cli/db-backup.php, has you change the database in data/config.php, and restores with cli/db-restore.php. Source: FreshRSS: Deploy FreshRSS with Docker (Docker Compose with PostgreSQL, Migrate database) checked 2026-09-30; FreshRSS docs: Backup (external database, cli/db-backup.php, migrating the database) checked 2026-09-30
With SQLite, the default
This is exactly what the builder writes for FreshRSS alone on example.org: the official definition with its published ports removed and Caddy added in front. The time zone is Etc/UTC here; the builder uses your browser's.
# docker-compose.yml built at dankhost.com for: FreshRSS # 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" # ---- FreshRSS (rss.example.org) ---- # Source: https://github.com/FreshRSS/FreshRSS/blob/edge/Docker/freshrss/docker-compose.yml (checked 2026-09-23) # Source: https://github.com/FreshRSS/FreshRSS/tree/edge/Docker (checked 2026-09-23) # Changed: TRUSTED_PROXY is narrowed from the documented '172.16.0.1/12 192.168.0.1/16' to Caddy's fixed address; TZ is your browser's time zone instead of the example Europe/Paris. # Uses the documented default SQLite database (the Postgres variant is an optional add-on file). freshrss: image: "freshrss/freshrss:latest" container_name: "freshrss" hostname: "freshrss" restart: "unless-stopped" logging: options: max-size: "10m" volumes: - "freshrss-data:/var/www/FreshRSS/data" - "freshrss-extensions:/var/www/FreshRSS/extensions" environment: TZ: "Etc/UTC" CRON_MIN: "3,33" TRUSTED_PROXY: "172.30.0.2" 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: freshrss-data: freshrss-extensions:
With PostgreSQL
This is what the builder's code writes for FreshRSS alone on example.org from the project's PostgreSQL setup (the builder on the front page still writes the SQLite version, so copy this one from here): the official definition with its published ports removed and Caddy added in front. The time zone is Etc/UTC here; the builder uses your browser's. Every ${VARIABLE} is defined in the .env below.
# docker-compose.yml built at dankhost.com for: FreshRSS # 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" # ---- FreshRSS (rss.example.org) ---- # Source: https://github.com/FreshRSS/FreshRSS/blob/edge/Docker/freshrss/docker-compose.yml (checked 2026-09-23) # Source: https://github.com/FreshRSS/FreshRSS/tree/edge/Docker (checked 2026-09-23) # Source: https://github.com/FreshRSS/FreshRSS/blob/edge/Docker/freshrss/docker-compose-db.yml (checked 2026-09-30) # Source: https://github.com/FreshRSS/FreshRSS/tree/edge/Docker (checked 2026-09-30) # Source: https://hub.docker.com/_/postgres (checked 2026-09-30) # Changed: TRUSTED_PROXY is narrowed from the documented '172.16.0.1/12 192.168.0.1/16' to Caddy's fixed address; TZ is your browser's time zone instead of the example Europe/Paris. # Adds the repository's docker-compose-db.yml, merged into this one file as docker compose -f docker-compose.yml -f docker-compose-db.yml would: the freshrss-db service running postgres:18 (the major version the file pins) with its data volume at /var/lib/postgresql, and DB_BASE, DB_USER and DB_PASSWORD in .env. # In the file POSTGRES_PASSWORD falls back to 'freshrss' when DB_PASSWORD is unset; here it has no fallback, so a missing .env value can never start the database with a known password. .env sets DB_PASSWORD to a random secret. # Left out: the file's example PostgreSQL tuning (command: -c shared_buffers=1GB -c work_mem=32MB). The file's own comment calls them examples and says to stick to the defaults when in doubt; 1 GB of shared buffers is more than a small home server should give one app. # freshrss-db sits only on the internal network it shares with freshrss, publishes no port and is not on the proxy network. freshrss: image: "freshrss/freshrss:latest" container_name: "freshrss" hostname: "freshrss" restart: "unless-stopped" logging: options: max-size: "10m" volumes: - "freshrss-data:/var/www/FreshRSS/data" - "freshrss-extensions:/var/www/FreshRSS/extensions" environment: TZ: "Etc/UTC" CRON_MIN: "3,33" TRUSTED_PROXY: "172.30.0.2" networks: proxy: {} freshrss-backend: {} freshrss-db: image: "postgres:18" container_name: "freshrss-db" hostname: "freshrss-db" restart: "unless-stopped" logging: options: max-size: "10m" volumes: - "freshrss-db:/var/lib/postgresql" environment: POSTGRES_DB: "${FRESHRSS_DB_BASE:-freshrss}" POSTGRES_USER: "${FRESHRSS_DB_USER:-freshrss}" POSTGRES_PASSWORD: "${FRESHRSS_DB_PASSWORD}" networks: freshrss-backend: {} 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" freshrss-backend: internal: true volumes: caddy-data: caddy-config: freshrss-data: freshrss-extensions: freshrss-db:
Caddyfile save as caddy/Caddyfile
Caddy gets and renews the HTTPS certificate for rss.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.
# FreshRSS
rss.example.org {
reverse_proxy freshrss:80
}
.env
With SQLite, the default
FreshRSS needs no secret here; the builder adds nothing you have to fill in by hand.
# .env for FreshRSS, from dankhost.com/app/freshrss/. Nothing here is secret. # Keep this file private (chmod 600). # None of the chosen apps needs a variable here.
With PostgreSQL
The secret is left blank here on purpose: a password printed on a public page is the same for everyone who copies it. Fill it with random letters and digits as in How to run it.
# .env for FreshRSS, from dankhost.com/app/freshrss/. Fill the blank secret before starting. # Keep this file private (chmod 600). # FreshRSS FRESHRSS_DB_BASE=freshrss FRESHRSS_DB_USER=freshrss # 32 random letters and digits, for example from: tr -dc A-Za-z0-9 </dev/urandom | head -c 32 FRESHRSS_DB_PASSWORD=
Changes from the official file
Besides prefixing every service, container, volume, folder and variable with freshrss (so any set of apps can share one file), these are all the differences from what the project documents:
With SQLite, the default
- TRUSTED_PROXY is narrowed from the documented '172.16.0.1/12 192.168.0.1/16' to Caddy's fixed address; TZ is your browser's time zone instead of the example Europe/Paris.
- Uses the documented default SQLite database (the Postgres variant is an optional add-on file).
Notes for FreshRSS behind the proxy
- The web installer runs on first visit and is open to whoever gets there first: open the address straight away, pick SQLite, and set the base URL to https://rss.example.org.
- Feeds refresh at minutes 3 and 33 of every hour (CRON_MIN).
With PostgreSQL
- TRUSTED_PROXY is narrowed from the documented '172.16.0.1/12 192.168.0.1/16' to Caddy's fixed address; TZ is your browser's time zone instead of the example Europe/Paris.
- Adds the repository's docker-compose-db.yml, merged into this one file as docker compose -f docker-compose.yml -f docker-compose-db.yml would: the freshrss-db service running postgres:18 (the major version the file pins) with its data volume at /var/lib/postgresql, and DB_BASE, DB_USER and DB_PASSWORD in .env.
- In the file POSTGRES_PASSWORD falls back to 'freshrss' when DB_PASSWORD is unset; here it has no fallback, so a missing .env value can never start the database with a known password. .env sets DB_PASSWORD to a random secret.
- Left out: the file's example PostgreSQL tuning (command: -c shared_buffers=1GB -c work_mem=32MB). The file's own comment calls them examples and says to stick to the defaults when in doubt; 1 GB of shared buffers is more than a small home server should give one app.
- freshrss-db sits only on the internal network it shares with freshrss, publishes no port and is not on the proxy network.
Notes for FreshRSS behind the proxy
- The web installer runs on first visit and is open to whoever gets there first: open the address straight away, pick PostgreSQL, and give host freshrss-db, user and database freshrss and the password FRESHRSS_DB_PASSWORD from .env; set the base URL to https://rss.example.org.
- Feeds refresh at minutes 3 and 33 of every hour (CRON_MIN).
How to run it
With SQLite, the default
- At your DNS provider, add an A record named
rsson your domain pointing at the server's public IP address, and forward TCP 80, TCP 443 and UDP 443 to it. - Save the three files in one folder:
docker-compose.ymland.envside by side, the Caddyfile at./caddy/Caddyfile. Replaceexample.orgwith your domain in the Caddyfile, the compose file and the .env, or let the builder do it. - Nothing in
.envneeds filling in;chmod 600 .envall the same. - Start it:
docker compose up -d docker compose logs -f caddy # watch the certificate arrive
- Open the new address (
rss.plus your domain) in a browser and follow the notes above.
With PostgreSQL
- At your DNS provider, add an A record named
rsson your domain pointing at the server's public IP address, and forward TCP 80, TCP 443 and UDP 443 to it. - Save the three files in one folder:
docker-compose.ymland.envside by side, the Caddyfile at./caddy/Caddyfile. Replaceexample.orgwith your domain in the Caddyfile, the compose file and the .env. - Fill the blank
FRESHRSS_DB_PASSWORDin.env. On the server,tr -dc A-Za-z0-9 </dev/urandom | head -c 32prints 32 random letters and digits. Thenchmod 600 .env. - Start it:
docker compose up -d docker compose logs -f caddy # watch the certificate arrive
- Open the new address (
rss.plus your domain) in a browser and follow the notes above.
Back it up
With SQLite, the default
FreshRSS's backup page: data/ is required (its cache/ can be skipped, FreshRSS rebuilds it) and extensions/ is recommended if you use third-party extensions. With the default SQLite the database is inside data/, so no separate dump is needed.
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: FreshRSS
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)
## FreshRSS
FreshRSS's backup page: data/ is required (its cache/ can be skipped, FreshRSS rebuilds it) and extensions/ is recommended if you use third-party extensions. With the default SQLite the database is inside data/, so no separate dump is needed.
What this compose mounts:
- freshrss-data (named volume, /var/www/FreshRSS/data in freshrss)
BACK UP: configuration, users and their SQLite databases.
- freshrss-extensions (named volume, /var/www/FreshRSS/extensions in freshrss)
BACK UP: third-party extensions you installed.
1. Stop freshrss. FreshRSS: 'It is safer to stop your web server and cron during maintenance operations'; in this image both run in the one container.
docker compose stop freshrss
2. Copy while freshrss is stopped:
docker run --rm --volumes-from freshrss -v "$BACKUP":/backup ubuntu tar cvf /backup/freshrss-data.tar /var/www/FreshRSS/data
docker run --rm --volumes-from freshrss -v "$BACKUP":/backup ubuntu tar cvf /backup/freshrss-extensions.tar /var/www/FreshRSS/extensions
3. Start it again:
docker compose start freshrss
Restore check:
tar tf "$BACKUP/freshrss-data.tar" > /dev/null && echo OK
tar tf "$BACKUP/freshrss-extensions.tar" > /dev/null && echo OK
Put a copy back (with freshrss stopped):
docker run --rm --volumes-from freshrss -v "$BACKUP":/backup ubuntu bash -c "cd /var/www/FreshRSS/data && tar xvf /backup/freshrss-data.tar --strip 4"
docker run --rm --volumes-from freshrss -v "$BACKUP":/backup ubuntu bash -c "cd /var/www/FreshRSS/extensions && tar xvf /backup/freshrss-extensions.tar --strip 4"
Stop it, restore both volumes with the commands above, start it.
Sources:
- FreshRSS docs: Backup: https://freshrss.github.io/FreshRSS/en/admins/05_Backup.html (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)
With PostgreSQL
FreshRSS's backup page: data/ is required (its cache/ can be skipped) and extensions/ is recommended if you use third-party extensions; an external PostgreSQL database is backed up separately, with cli/db-backup.php or pg_dump. This plan uses pg_dump.
Below is the BACKUP.md for the PostgreSQL version of the compose file above, written by the same code as the builder's: which of its folders and volumes hold data, the dump command the project documents, rewritten for this file's service names, what to copy with which container stopped, and a restore check.
# BACKUP.md built at dankhost.com for: FreshRSS
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)
## FreshRSS
FreshRSS's backup page: data/ is required (its cache/ can be skipped) and extensions/ is recommended if you use third-party extensions; an external PostgreSQL database is backed up separately, with cli/db-backup.php or pg_dump. This plan uses pg_dump.
What this compose mounts:
- freshrss-data (named volume, /var/www/FreshRSS/data in freshrss)
BACK UP: configuration (with the database settings) and users.
- freshrss-extensions (named volume, /var/www/FreshRSS/extensions in freshrss)
BACK UP: third-party extensions you installed.
- freshrss-db (named volume, /var/lib/postgresql in freshrss-db)
COVERED BY THE COMMAND BELOW: PostgreSQL's data files; the pg_dump below is the copy to keep.
1. Stop freshrss. FreshRSS: 'It is safer to stop your web server and cron during maintenance operations'; in this image both run in the one container. The database keeps running for the dump.
docker compose stop freshrss
2. Database dump for freshrss-db:
docker compose exec -T freshrss-db pg_dump -U freshrss freshrss | gzip -9 > "$BACKUP/freshrss-postgres-backup.sql.gz"
The command from FreshRSS's Docker README (Migrate database), with this file's service name; user and database are both freshrss (DB_USER and DB_BASE in .env).
3. Copy while freshrss is stopped:
docker run --rm --volumes-from freshrss -v "$BACKUP":/backup ubuntu tar cvf /backup/freshrss-data.tar /var/www/FreshRSS/data
docker run --rm --volumes-from freshrss -v "$BACKUP":/backup ubuntu tar cvf /backup/freshrss-extensions.tar /var/www/FreshRSS/extensions
4. Start it again:
docker compose start freshrss
Restore check:
zcat "$BACKUP/freshrss-postgres-backup.sql.gz" | grep -c 'PostgreSQL database dump complete' # 1 means pg_dump finished
tar tf "$BACKUP/freshrss-data.tar" > /dev/null && echo OK
tar tf "$BACKUP/freshrss-extensions.tar" > /dev/null && echo OK
Put a copy back (with freshrss stopped):
docker run --rm --volumes-from freshrss -v "$BACKUP":/backup ubuntu bash -c "cd /var/www/FreshRSS/data && tar xvf /backup/freshrss-data.tar --strip 4"
docker run --rm --volumes-from freshrss -v "$BACKUP":/backup ubuntu bash -c "cd /var/www/FreshRSS/extensions && tar xvf /backup/freshrss-extensions.tar --strip 4"
The dump goes into an empty database: on a new server, or after removing the db volume, start only freshrss-db (on first start it creates an empty freshrss database), load the dump, and start the rest:
docker compose up -d freshrss-db
until docker compose exec -T freshrss-db pg_isready -h 127.0.0.1 -U freshrss; do sleep 2; done # waits until the first-start setup is over
gunzip --stdout "$BACKUP/freshrss-postgres-backup.sql.gz" | docker compose exec -T freshrss-db psql -U freshrss -d freshrss --set ON_ERROR_STOP=on
docker compose up -d
Sources:
- FreshRSS docs: Backup (external database, cli/db-backup.php, migrating the database): https://freshrss.github.io/FreshRSS/en/admins/05_Backup.html (checked 2026-09-30)
- FreshRSS: Deploy FreshRSS with Docker (Docker Compose with PostgreSQL, Migrate database): https://github.com/FreshRSS/FreshRSS/tree/edge/Docker (checked 2026-09-30)
Update it
With SQLite, the default
What docker compose pull does depends only on how each image line in the compose file above is tagged. For FreshRSS as this page writes it:
| Service | Image | How it is pinned | What docker compose pull does |
|---|---|---|---|
caddy | caddy:2 | Major version only (tag 2) | Takes the newest image tagged 2: minor and patch releases of 2, never 3. A new major version needs a tag edit. |
freshrss | freshrss/freshrss:latest | Not pinned: moving tag latest | Moves to the newest image published as latest, which can be a new major version. |
What FreshRSS's docs say about updating
FreshRSS's Docker README updates a Compose install with docker compose pull followed by docker compose up -d.
- FreshRSS publishes latest as its versioned release and edge as its rolling release; this file uses latest.
The steps
- Back up first, as in Back it up above. An update can migrate FreshRSS's data on its first start; the copy is the way back.
- Download the new images. Running containers are not touched yet:
docker compose pull
- Recreate the containers whose image changed. Volumes and bind-mounted folders stay as they are:
docker compose up -d
- Watch FreshRSS start (Ctrl+C stops following the log, not the app):
docker compose logs -f freshrss
- 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
With PostgreSQL
What docker compose pull does depends only on how each image line in the compose file above is tagged. For FreshRSS as this page writes it:
| Service | Image | How it is pinned | What docker compose pull does |
|---|---|---|---|
caddy | caddy:2 | Major version only (tag 2) | Takes the newest image tagged 2: minor and patch releases of 2, never 3. A new major version needs a tag edit. |
freshrss | freshrss/freshrss:latest | Not pinned: moving tag latest | Moves to the newest image published as latest, which can be a new major version. |
freshrss-db database | postgres:18 | Major version only (tag 18) | Takes the newest image tagged 18: minor and patch releases of 18, never 19. A new major version needs a tag edit. |
Do not raise the major version of freshrss-db by editing its tag. Keep its tag, 18, as it is when you update FreshRSS.
PostgreSQL's docs: a new major version may change how data is stored on disk, so a data folder written by an older major version will not start under a newer one (the server refuses it). Moving needs a dump and restore (pg_dumpall, then load the dump into the new version) or pg_upgrade. Minor releases of the same major version never change the storage format. Source: PostgreSQL docs: Upgrading a PostgreSQL Cluster checked 2026-09-30
What FreshRSS's docs say about updating
FreshRSS's Docker README updates a Compose install with docker compose pull followed by docker compose up -d.
- FreshRSS publishes latest as its versioned release and edge as its rolling release; this file uses latest.
- FreshRSS and PostgreSQL are updated separately, one tag at a time. The freshrss-db tag, 18, takes every 18.x release on docker compose pull; PostgreSQL says minor releases never change the storage format, so that is safe.
- A new PostgreSQL major version cannot open the data of the old one (PostgreSQL's Upgrading a PostgreSQL Cluster page: dump and restore, or pg_upgrade). FreshRSS's Docker README gives its own way for a major-version move: keep FreshRSS stopped, back every user up to SQLite with cli/db-backup.php, remove the old database container and its volume, edit the tag, start the new, empty database, and restore the users with cli/db-restore.php. With this file's names, after the pg_dump backup above:
docker compose stop freshrss docker compose run --rm freshrss cli/db-backup.php docker compose rm -sf freshrss-db docker volume ls --filter name=freshrss-db # its full name starts with your project name; then: docker volume rm <that name> docker compose up -d freshrss-db # after editing the tag until docker compose exec -T freshrss-db pg_isready -h 127.0.0.1 -U freshrss; do sleep 2; done # waits until the first-start setup is over docker compose run --rm freshrss cli/db-restore.php --delete-backup docker compose up -d freshrss
- The README removes the old container and volume with docker compose down --volumes freshrss-db. In a file shared with other apps the steps above do it by name instead, so no other volume can go with it.
The steps
- Back up first, as in Back it up above. An update can migrate FreshRSS's data on its first start and its database with it; the copy is the way back.
- Download the new images. Running containers are not touched yet:
docker compose pull
- Recreate the containers whose image changed. Volumes and bind-mounted folders stay as they are:
docker compose up -d
- Watch FreshRSS start (Ctrl+C stops following the log, not the app):
docker compose logs -f freshrss
- 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
Locked out? Reset the admin password
Sets a new password for a FreshRSS user with its own command-line tools, run as www-data as its Docker guide does.
- List the users: Source: FreshRSS Docker README: Command line read 2026-10-03
docker compose exec --user www-data freshrss cli/list-users.php
- Set the new password (update-user.php takes the same options as create-user.php): Source: FreshRSS CLI README: create-user.php and update-user.php read 2026-10-03; FreshRSS Docker README: Command line read 2026-10-03
docker compose exec --user www-data freshrss cli/update-user.php --user '<user>' --password '<new password>'
Sources
Every page below was fetched on the date shown.
- FreshRSS README checked 2026-09-23 (what it does)
- FreshRSS README (Requirements) checked 2026-09-23 (hardware requirements)
- FreshRSS: Docker/freshrss/docker-compose.yml checked 2026-09-23 (compose definition and proxy settings, PostgreSQL version)
- FreshRSS: Deploy FreshRSS with Docker (TRUSTED_PROXY, CRON_MIN) checked 2026-09-23 (compose definition and proxy settings, update notes, PostgreSQL version, PostgreSQL backup plan, PostgreSQL update notes)
- 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)
- FreshRSS docs: Backup checked 2026-09-24 (backup plan, PostgreSQL version, PostgreSQL backup plan)
- Docker docs: Volumes, Back up, restore, or migrate data volumes checked 2026-09-24 (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)
- FreshRSS: Docker/freshrss/docker-compose-db.yml (PostgreSQL add-on file) checked 2026-09-30 (PostgreSQL version)
- Docker Official Image postgres: POSTGRES_USER, POSTGRES_PASSWORD, POSTGRES_DB, PGDATA (changed in 18) checked 2026-09-30 (PostgreSQL version)
- PostgreSQL docs: Upgrading a PostgreSQL Cluster checked 2026-09-30 (PostgreSQL update notes, database upgrade)