The console on :latest won't come back after a restart: each start adds another IPv6 listener, and nginx refuses the duplicate and exits. Reported in #135.
Main fixed this in #139, but that only reached the 27.1 release candidates, and those never move :latest. This brings the same fix to the 2026.10 line, on a new release/2026 branch cut from v2026.10.26.2, and sets the version to 2026.10.26.3.
Nothing else from main comes along.
The test also runs in the GitHub build now, since that's where the build happens. Main has the same gap and needs its own PR.
Checked locally: all CI steps, and the built image through three restarts, answering on IPv4 and IPv6.
The console on `:latest` won't come back after a restart: each start adds another IPv6 listener, and nginx refuses the duplicate and exits. Reported in #135.
Main fixed this in #139, but that only reached the 27.1 release candidates, and those never move `:latest`. This brings the same fix to the 2026.10 line, on a new `release/2026` branch cut from `v2026.10.26.2`, and sets the version to 2026.10.26.3.
Nothing else from main comes along.
The test also runs in the GitHub build now, since that's where the build happens. Main has the same gap and needs its own PR.
Checked locally: all CI steps, and the built image through three restarts, answering on IPv4 and IPv6.
listen-ipv6.sh writes "listen [::]:8080;" and then looked for
"listen [::]:8080" with one space, so the check never matched. A new
container was fine; restarting the same one (a reboot, docker restart, or
an installer that stops and starts the stack) added a second listener,
and nginx refused the duplicate and restarted in a loop. The check now
allows any number of spaces.
docker/listen-ipv6.test.sh runs the script on nginx.conf three times and
checks for one IPv6 listener; CI runs it, on both forges.
From ee96410 on main, for the 2026.10 line that :latest still points at.
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 console on
:latestwon't come back after a restart: each start adds another IPv6 listener, and nginx refuses the duplicate and exits. Reported in #135.Main fixed this in #139, but that only reached the 27.1 release candidates, and those never move
:latest. This brings the same fix to the 2026.10 line, on a newrelease/2026branch cut fromv2026.10.26.2, and sets the version to 2026.10.26.3.Nothing else from main comes along.
The test also runs in the GitHub build now, since that's where the build happens. Main has the same gap and needs its own PR.
Checked locally: all CI steps, and the built image through three restarts, answering on IPv4 and IPv6.