novox/mesh-catalog
3
0
Fork 0
Code Issues Pull Requests 1 Packages Projects Releases Wiki Activity

route-proxy: the server container resolves its own built artifact

Browse Source 
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.
This commit is contained in:
jschoubben
2026-09-25 18:09:09 +02:00
parent 3147fac08b
commit 4c5e69903f
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
modules/route-proxy/module.json
+1 -1
View File
@@ -95,7 +95,7 @@
"id": "server", "id": "server",
"type": "container", "type": "container",
"name": "route-proxy", "name": "route-proxy",
"image": "mesh-route-proxy@sha256:0000000000000000000000000000000000000000000000000000000000000000", "artifact": "server",
"network": "host", "network": "host",
"env-file": [ "env-file": [
"/var/lib/route-proxy/acme.env" "/var/lib/route-proxy/acme.env"