From 1b02dc1f66cc06f5b797d0e69c4818c361adbbe9 Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 25 Sep 2026 17:10:56 +0200 Subject: [PATCH] builder: qualify its own image with the registry host MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Bare mesh-builder@sha256:... is only resolvable for a module with a build section — the mesh's own build step rewrites the reference to a real registry path as part of resolving build.artifacts. builder is handed over, not built, so nothing ever rewrites it: pushed as written, docker read it literally and tried Docker Hub. Took the live node's mesh-builder down for the length of one push-and-fix (docker: pull access denied for mesh-builder, repository does not exist). novox.internal:5100, not the literal external IP docker inspect showed live, for the same reason addresses generally don't get hardcoded in this catalogue. --- modules/builder/module.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/builder/module.json b/modules/builder/module.json index 8e32ccc..229ca97 100644 --- a/modules/builder/module.json +++ b/modules/builder/module.json @@ -50,7 +50,7 @@ "id": "server", "type": "container", "name": "mesh-builder", - "image": "mesh-builder@sha256:42f5203a6838776447790d9e7d27f22a56e9462bdd25401645f22d188da56704", + "image": "novox.internal:5100/mesh-builder@sha256:42f5203a6838776447790d9e7d27f22a56e9462bdd25401645f22d188da56704", "env-file": [ "/var/lib/mesh/builder/builder.env" ],