From 30b7ce429cddae5094ec86ac90dbe47ceba90a24 Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 25 Sep 2026 23:59:42 +0200 Subject: [PATCH] automx: the schema its seed writes belongs to one automx2, so that one is named MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit An unpinned pip install took the latest automx2, whose schema grew a column (server.prio) the module's own seeding SQL predates — a 500 on every autoconfig request against a table the seed had just written. 2021.6 is what the proven image runs; the seed and the software agree again. Regenerating the seed for a newer automx2 is its own change, made deliberately, not by whatever pip resolved this week. --- modules/mailu/automx/Dockerfile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/mailu/automx/Dockerfile b/modules/mailu/automx/Dockerfile index 80ae1b9..c48cab2 100644 --- a/modules/mailu/automx/Dockerfile +++ b/modules/mailu/automx/Dockerfile @@ -19,7 +19,7 @@ RUN chmod u+x setupvenv.sh start add-domains setup setup-db RUN ./setupvenv.sh \ && . .venv/bin/activate \ - && pip install automx2 + && pip install automx2==2021.6 # The launcher `start` expects. In the predecessor's image this wrapper appeared during a build # step that never made it into the files this module carries — the image worked and the recipe -- 2.54.0