Debian 13 (trixie) rebase: docker, debian-live-config, and pi-gen builds.
All three build targets move from Debian 12/bookworm to Debian 13/trixie
for fresh installs; existing Debian 12 systems remain supported in place.
Docker: api/help on python:3.13-trixie, controller on 3.13-slim-trixie,
app on node:20-trixie (matches trixie's nodejs 20), samba/zim on
debian:13. Full backend suite passes on Python 3.13 in the api container.
debian-live-config: --distribution trixie; postgres teardown for the
SQLite cutover (pg_dropcluster hook block removed, wrolpi-bootstrap.sh no
longer creates a cluster or calls the deleted initialize_api_db.sh — the
API creates wrolpi.db itself on first start). README documents the
SQLite layout and drops Etcher recommendations.
pi-gen: upstream has no trixie branch — the arm64 branch now defaults to
RELEASE=trixie; KEYBOARD_KEYMAP=en_US is rejected by trixie's
console-setup (ckbcomp validates), use 'us'; stop stamping a Postgres
.pgpass into /etc/skel.
Package lists (both targets): postgresql-15/postgresql-doc/libpq-dev
deleted; libtiff5-dev renamed to libtiff-dev; software-properties-common
and cpufrequtils removed from trixie (Controller CPU throttle falls back
to sysfs, dead cpufreq-set sudoers rule removed); locales and gnupg added
(no longer arrive transitively under --apt-recommends false); sqlite3 CLI
added for reset_tags.sh.
help.sh: replace the Postgres service/port/socket/cluster/psql checks
(all false FAILEDs after the SQLite cutover) with SQLite checks:
wrolpi.db exists, PRAGMA quick_check, file_group table + row count, run
as the wrolpi user so root never creates the -shm sidecar.
Both build scripts take a WROLPI_BUILD_DIR override so development builds
can run beside the release pipeline's build trees; the sudo re-exec
passes it through explicitly (a plain sudo would drop it).
test_common.py: the truncate tests hard-coded sys.getsizeof results from
the 3.11 object layout (str/list shrank in 3.12); assert the contract
(fits budget, prefix, monotonic in budget) so they pass on 3.11 and 3.13.
Verified: trixie ISO (3.7G) and pi-gen desktop image (4.3G) both built
from scratch and passed their sanity checks.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-13 15:16:00 -06:00
|
|
|
FROM python:3.13-trixie
|
2021-11-01 16:42:52 -06:00
|
|
|
ENV DOCKER=true
|
2026-10-22 19:28:27 -06:00
|
|
|
# Deno trusts the system store, which apt keeps current, instead of its bundled roots.
|
|
|
|
|
ENV DENO_TLS_CA_STORE=system
|
2021-11-01 16:42:52 -06:00
|
|
|
WORKDIR /opt/wrolpi
|
|
|
|
|
|
|
|
|
|
# Update dependencies for the services install.
|
A WROLPi serves its library over rsync, and makes a database snapshot on request (#988)
* A WROLPi serves its library over rsync, and makes a database snapshot on request
The first part of replacing the sync: a secondary will copy its primary's whole media directory with rsync and
replace its database with the primary's, instead of downloading the files of FileGroups over HTTP (which never
copies an ignored directory, such as the map's).
- An rsync daemon serves the media directory read-only on port 8873, on every WROLPi. It never serves the TLS keys,
the cookies, or the database in use. On a Raspberry Pi and Debian it is the wrolpi-rsyncd unit; in Docker the
Controller runs it in a helper container made from the api container (its image, user and volumes), so the media
directory is still configured in one place. All three read controller/rsyncd.conf.
- POST /api/sync/snapshot asks for a snapshot of the database, which the daemon serves from config/.sync. An
unchanged database is not written again.
- /api/sync/info also says the database's migration and whether the media directory is mounted.
Nothing uses these yet; the existing sync is unchanged.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* The rsync daemon follows no links, and no snapshot is made in WROL Mode
- A client that asked the daemon to follow symbolic links could read what a link in the library points at. A
relative link to config/ssl was read this way although that directory is left out of the module. The daemon now
refuses the three options that follow links; a link is sent as a link.
- A database snapshot is a new file on the primary's drive, so WROL Mode refuses it, as it does a backup. A snapshot
made earlier is still served.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* No rsync helper from an image without rsync, and the helper follows the api container
Review found:
- A helper made from an api image built before rsync was added exits at once, and Docker restarted it forever while
the Controller reported it created. The image is now looked at first; no helper is made from one without rsync,
an older helper is left serving, and the reason is logged once.
- The helper was only checked when the Controller started, so a recreated or rebuilt api container left it stale.
It is now checked every minute.
- A snapshot cut off by its process being killed stayed marked as running and held back every later request.
- The snapshot's half-written temporary file was served by the daemon.
- The comment on the daemon's refused options claimed more than they give: a link that is part of the requested
path is still followed.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
---------
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
2026-11-18 16:47:02 -07:00
|
|
|
RUN apt-get update && apt-get install -y ffmpeg catdoc sysstat aria2 iputils-ping unrar-free unzip rsync \
|
2026-04-11 20:09:30 -06:00
|
|
|
build-essential libsqlite3-dev zlib1g-dev git
|
|
|
|
|
|
|
|
|
|
# Install tippecanoe (for map search index building via tippecanoe-decode).
|
|
|
|
|
RUN git clone --depth 1 --branch 2.79.0 https://github.com/felt/tippecanoe.git /tmp/tippecanoe \
|
|
|
|
|
&& cd /tmp/tippecanoe && make -j$(nproc) && make install \
|
|
|
|
|
&& rm -rf /tmp/tippecanoe \
|
|
|
|
|
&& tippecanoe-decode --help 2>&1 | head -1
|
2022-03-08 13:26:03 -07:00
|
|
|
RUN ffmpeg -version
|
2026-02-20 14:37:58 -07:00
|
|
|
|
2026-06-24 15:12:27 -06:00
|
|
|
# Install Deno runtime for yt-dlp. yt-dlp's EJS challenge solver requires Deno >=2.3.0; pin
|
|
|
|
|
# v2.8.3 to match scripts/upgrade.sh and docker/archive/Dockerfile.
|
|
|
|
|
RUN DENO_VERSION="v2.8.3" \
|
|
|
|
|
&& ARCH=$(uname -m) \
|
|
|
|
|
&& if [ "$ARCH" = "aarch64" ]; then \
|
|
|
|
|
DENO_ARCH="aarch64-unknown-linux-gnu"; \
|
|
|
|
|
DENO_SHA256="d4589cc1ffcbf1995c92a0127d932aaf832ac70cfdcc6d5b7bf38043cf303575"; \
|
|
|
|
|
elif [ "$ARCH" = "x86_64" ]; then \
|
|
|
|
|
DENO_ARCH="x86_64-unknown-linux-gnu"; \
|
|
|
|
|
DENO_SHA256="30455b845ffa6082209c3590269c910ad3b7efdf28c9879afd4006c47ae54197"; \
|
|
|
|
|
else echo "Unsupported architecture: $ARCH" && exit 1; fi \
|
|
|
|
|
&& curl -fsSL "https://github.com/denoland/deno/releases/download/${DENO_VERSION}/deno-${DENO_ARCH}.zip" -o /tmp/deno.zip \
|
|
|
|
|
# Assert the hash to avoid malicious or invalid files.
|
|
|
|
|
&& echo "${DENO_SHA256} /tmp/deno.zip" | sha256sum -c - \
|
|
|
|
|
&& unzip -o /tmp/deno.zip -d /usr/local/bin/ \
|
2026-02-20 14:37:58 -07:00
|
|
|
&& chmod +x /usr/local/bin/deno \
|
|
|
|
|
&& rm /tmp/deno.zip \
|
|
|
|
|
&& deno --version
|
|
|
|
|
|
2024-05-18 19:13:41 -06:00
|
|
|
# yt-dlp needs cache directory
|
|
|
|
|
RUN mkdir /.cache && chown -R 1000:1000 /.cache
|
2021-11-01 16:42:52 -06:00
|
|
|
|
Python packages install from hash-locked requirements; yt-dlp still floats (#913)
* Python packages install from hash-locked requirements; yt-dlp still floats
Every pip install trusted PyPI over TLS: requirements.txt pins only top-level versions
(some with >=), the controller's are almost all >=, and dependencies were never pinned, so
a forged certificate (as the eMudhra key compromise allowed) could change code in the API,
the controller, or the archive container. scripts/lock_requirements.sh generates a
universal, hash-locked .lock beside each requirements.txt, and
install_python_requirements.sh installs it with --require-hashes at every site. yt-dlp is
left out of the lock and upgraded afterwards so devices still get YouTube fixes; its
dependencies are locked. The unpinned `pip install --upgrade pip` steps are gone.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* The unhashed yt-dlp install cannot replace locked packages, and nothing builds from source
Review of #913 found two holes. The yt-dlp step ran without --no-deps, so pip's
only-if-needed strategy would still fetch an unhashed dependency whenever yt-dlp's metadata
asked for a version the lock did not install. And srt is published only as a source
archive, whose build installed setuptools with hash checking off on every install.
The yt-dlp step now uses --no-deps (its dependencies come only from the lock), both steps
are retried as the image builds did before, and installs and locks are wheels-only. srt
3.5.3 is vendored unmodified as wrolpi/vendor/srt.py (MIT), verified against the sdist
hash the lock pinned; webvtt-py's SRT reader rejects WROLPi's own test file, so it is not
a replacement.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-01 12:00:29 -07:00
|
|
|
# Install dependencies from the hash-locked requirements.
|
|
|
|
|
COPY requirements.txt requirements.lock /opt/wrolpi/
|
|
|
|
|
COPY scripts/install_python_requirements.sh /opt/wrolpi/scripts/install_python_requirements.sh
|
|
|
|
|
RUN /opt/wrolpi/scripts/install_python_requirements.sh pip3 /opt/wrolpi/requirements.txt
|
2024-04-17 11:25:26 -06:00
|
|
|
|
|
|
|
|
# Install WROLPi.
|
2021-11-01 16:42:52 -06:00
|
|
|
COPY main.py /opt/wrolpi/
|
|
|
|
|
COPY wrolpi /opt/wrolpi/wrolpi
|
|
|
|
|
COPY modules /opt/wrolpi/modules
|
|
|
|
|
|
2025-12-19 16:42:36 -07:00
|
|
|
ENTRYPOINT [ "python3", "/opt/wrolpi/main.py"]
|
2025-12-16 19:20:04 -07:00
|
|
|
# Log level controlled by LOG_LEVEL env var or wrolpi.yaml config (default: info)
|
|
|
|
|
CMD ["api", "--host", "0.0.0.0"]
|