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 (mesh-catalog#63) — control plane and build machine both upgraded live to understand it.
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 (mesh-catalog#63) — control plane and build machine both upgraded live to understand it.
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.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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 (mesh-catalog#63) — control plane and build machine both upgraded live to understand it.