Backport of #66 (#65): the project network gets IPv6 on a machine that has it, and deps offers ip6tables for Docker before 27. Conflicts were only #48 context that this line does not have.
Pins: server 2026.11.11 (from 2026.10.29.1), console 2026.10.26.7 (from 2026.10.26.5); webmail unchanged. Tarballs checked against each release's SHA256SUMS.
Cherry-pick of bad9a5a: upgrade-containers read the archive listing through grep -q under pipefail and failed when tar got SIGPIPE.
e2e on this branch (Debian 13 lab): install-local 26, install-public 20, install-host 44, upgrade-containers 17 and upgrade-host-server 11 (OLD_REF=v2026.10.15.2), ipv6-sources 11, proxy-snippets 13. All green.
The stable line for 2026.11.15:
- Backport of #66 (#65): the project network gets IPv6 on a machine that has it, and deps offers ip6tables for Docker before 27. Conflicts were only #48 context that this line does not have.
- Pins: server 2026.11.11 (from 2026.10.29.1), console 2026.10.26.7 (from 2026.10.26.5); webmail unchanged. Tarballs checked against each release's SHA256SUMS.
- Cherry-pick of bad9a5a: upgrade-containers read the archive listing through `grep -q` under pipefail and failed when tar got SIGPIPE.
e2e on this branch (Debian 13 lab): install-local 26, install-public 20, install-host 44, upgrade-containers 17 and upgrade-host-server 11 (OLD_REF=v2026.10.15.2), ipv6-sources 11, proxy-snippets 13. All green.
The network the installer writes was IPv4 only. Docker relays an IPv6
connection to a published port of an IPv4-only container through
docker-proxy, so the server saw every client that connected over IPv6 as
the network's gateway, 172.31.253.1: SPF, DMARC and iprev were checked
against it, IPv6 senders shared one set of bans and rate limits, and
with --proxy snippets (or front ends on the host) the gateway is on the
server's allowed list, so IPv6 clients were never banned at all.
On a machine with IPv6, compose.yaml now gives the network a unique
local /64 (fd69:6e62:7578::/64) beside the IPv4 subnet. Re-running
install converges an existing deployment: compose recreates the network.
That is enough with Docker 27 and later and with podman, which forward
both families themselves. Docker before 27 still relays IPv6 unless
ip6tables is on, which there also takes "experimental" (with ip6tables
alone the daemon does not start). The survey now reads the engine
version and /etc/docker/daemon.json, and deps offers to set both keys,
keeping the old file as daemon.json.before-inbuxa and putting it back if
Docker does not come up on the new one. Without --install-deps the plan
warns instead, and it never writes over a daemon.json it cannot parse.
Outbound mail is unchanged in practice: the server tries IPv4 first by
default and uses IPv6 only for hosts that have no IPv4 address.
e2e/cases/ipv6-sources.sh opens SMTP sessions from a second network
namespace with addresses of its own; with OLD_REF it shows the bug on an
install from before the fix, then converges it.
Fixes#65
grep -q stops reading at its first match; under pipefail the tar it
cut off fails the pipeline, so the check said an archive with
config.json in it had none. Seen on the 27.1-rc.15 pins, where
config.json comes third of 33 entries.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The stable line for 2026.11.15:
bad9a5a: upgrade-containers read the archive listing throughgrep -qunder pipefail and failed when tar got SIGPIPE.e2e on this branch (Debian 13 lab): install-local 26, install-public 20, install-host 44, upgrade-containers 17 and upgrade-host-server 11 (OLD_REF=v2026.10.15.2), ipv6-sources 11, proxy-snippets 13. All green.