From dd5b973e66e549cf22891c1d8d158522b98ddba2 Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 25 Sep 2026 17:58:10 +0200 Subject: [PATCH] route-proxy: declare the build context its own Dockerfile has always needed MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The Dockerfile's own comment already said it — 'the build context is the mesh-controller repository root' — but nothing in the manifest actually said so to the mesh, so every build attempt used mesh-catalog's own directory instead and failed with 'stat go.mod: file does not exist'. Never caught before because route-proxy has never been assigned anywhere. Uses the context mechanism just added (mesh-controller#62), proven working tonight on builder's own self-build. --- modules/route-proxy/module.json | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/modules/route-proxy/module.json b/modules/route-proxy/module.json index aecaca4..f5d42c0 100644 --- a/modules/route-proxy/module.json +++ b/modules/route-proxy/module.json @@ -123,7 +123,11 @@ { "name": "server", "kind": "image", - "from": "Dockerfile" + "from": "Dockerfile", + "context": { + "repository": "https://git.novox.be/novox/mesh-controller.git", + "ref": "main" + } }, { "name": "trust",