dig +short prints its own errors (";; no servers could be reached") on
stdout, and the check counted any line that was not 127.x or 0.0.0.0 as
an address, so with a dead resolver the fallback to 1.1.1.1 never ran
and the install failed further on. Count only address lines.
The original resolv.conf was put back only after a successful install;
any failure left the container on 1.1.1.1, and a second run then saved
that as the backup. Restore it on exit.
The install ran as a plain pct exec, so its output only reached the
terminal and every failure was reported as "pct exited with status 100"
with nothing after the step. It now runs through $STD: the output goes to
the run log, and a failure shows it and puts it in the trace. Inside the
container the helpers ran in silent mode as well, which kept apt's own
error in a log there; VERBOSE=yes prints it instead.
A failed download of core.func or tools.func was sourced as an empty
file and ended in "load_functions: command not found" (exit 127, 7 of
the 22 failed runs in four days). It now stops with exit 7 and says the
container could not download them.
Snapshots follow a container's settings as [name] sections, so the two
lxc lines appended with >> landed in the last snapshot: pct config never
showed them, the container got no /dev/net/tun and tailscaled could not
start. The grep that skips an existing line also matched the snapshot's
copy on a second run. Check and insert them in the container's own
section.
New installs get the latest v1 release. Existing 0.16 installs are
brought to 0.16.27 first, then update runs stalwart-migrate: prepare
asks its questions, the final run copies the RocksDB store to a new
-v1 directory, and v1 starts on it. The 0.16 store and its config stay
in place for a rollback.
The migration only runs from the container console, needs room for a
second copy of the store and only handles the default RocksDB backend.
If the copy fails, 0.16 is started again.
Bump OpenResty to 1.31.8.1 (the version NPM 2.17 ships) and apply the
upstream nginx 1.31.9 HTTP/2 fixes on top of its bundled nginx 1.31.8.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
New scripts take their authors from the Author header. Pull requests of
services and the website are collected like those of core. Releases mention
contributors, are no longer cut at 5000 characters, link the compare view,
and are skipped on days without changes.
* Add aiostreams (ct)
* AIOStreams: drop mimalloc, cap the heap, add ffprobe
Testing in an LXC showed lower and steadier memory without the mimalloc
preload. The service now runs with NODE_ENV=production, a heap cap of
half the container RAM and MALLOC_ARENA_MAX=2.
ffmpeg provides ffprobe for the media info probe, which is on by
default.
The commit lookup for metadata.json no longer aborts the install when
the GitHub API rate limit is hit.
---------
Co-authored-by: push-app-to-main[bot] <203845782+push-app-to-main[bot]@users.noreply.github.com>
Co-authored-by: MickLesk <47820557+MickLesk@users.noreply.github.com>
changedetection.io recommends its own SockPuppetBrowser since 2024. Chrome now comes from Google's repository and runs as a dedicated user under SockPuppetBrowser, which installs from its releases. Updates no longer build Browserless or download every Playwright browser; existing containers migrate once, keeping a custom PLAYWRIGHT_DRIVER_URL.
Based on #18613 by skkzsh.