From 4c5e69903f3bebecac4215876ca8cc3d917755a4 Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 25 Sep 2026 18:09:09 +0200 Subject: [PATCH] route-proxy: the server container resolves its own built artifact MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Was still pinned to the scaffold's placeholder digest (mesh-route- proxy@sha256:0000...0000) even after the build+context work landed — never caught because nothing had assigned route-proxy before tonight. artifact: server, matching trust's own reference a few lines up and every other built module in the catalogue. --- modules/route-proxy/module.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/route-proxy/module.json b/modules/route-proxy/module.json index f5d42c0..534970a 100644 --- a/modules/route-proxy/module.json +++ b/modules/route-proxy/module.json @@ -95,7 +95,7 @@ "id": "server", "type": "container", "name": "route-proxy", - "image": "mesh-route-proxy@sha256:0000000000000000000000000000000000000000000000000000000000000000", + "artifact": "server", "network": "host", "env-file": [ "/var/lib/route-proxy/acme.env" -- 2.54.0