maathimself/mailflow v3.4.4

on GitHub

MailFlow v3.4.4

A fix for a startup regression introduced in 3.4.3.

Fixes

• The container starts again on a read-only root filesystem (#453): 3.4.3 generated the nginx config at container start, so /etc/nginx/conf.d had to be writable. Anyone running with read_only: true — common under Kubernetes and hardened Docker setups — got a failed write, and because the nginx entrypoint runs under set -e, the container never started at all. The config is baked into the image again, and only the resolver line is adjusted at startup. If the filesystem is read-only that adjustment is skipped, the shipped default applies, and the container starts normally.

  The 3.4.3 fix for #448 is unaffected: the resolver is still read from the container's own /etc/resolv.conf, so Podman, Kubernetes and other non-Docker networks keep working.

Upgrading

Pull the new images and recreate. No configuration change, no migrations.

If you run read-only and on a non-Docker network, mount a file over /etc/nginx/conf.d/default.conf with your own resolver, since the automatic detection cannot write on a read-only filesystem. A bare --read-only with no writable mounts has never worked, in any version, because the self-signed certificate needs somewhere to be written.