route-proxy: declare the build context its own Dockerfile has always needed #64

Merged

jschoubben merged 1 commits from feat/route-proxy-declares-its-real-context into main

2026-09-25 15:58:20 +00:00

Author	SHA1	Message	Date
jschoubben	dd5b973e66	route-proxy: declare the build context its own Dockerfile has always needed 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.	2026-09-25 17:58:10 +02:00

Author

SHA1

Message

Date

jschoubben

dd5b973e66

route-proxy: declare the build context its own Dockerfile has always needed

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.

2026-09-25 17:58:10 +02:00