The catalogue builds its own runtime, and postgres serves its tools

Both modules keep their tools in an entrypoint of their own, so an image that named only the consumer would serve none of them.
2026-09-13 01:13:43 +02:00
parent d6c9c8d666
commit e742b6a569
3 changed files with 48 additions and 5 deletions
@@ -60,7 +60,6 @@
      "id": "runtime",
      "type": "container",
      "name": "mesh-catalog",
-      "image": "mesh-runtime-mesh-catalog@sha256:0000000000000000000000000000000000000000000000000000000000000000",
      "network": "host",
      "volumes": [
        "/var/lib/mesh/mesh-catalog/broker:/run/secrets/broker:ro",
@@ -71,7 +70,21 @@
      },
      "env-file": [
        "/var/lib/mesh-catalog/db.env"
+      ],
+      "artifact": "runtime",
+      "args": [
+        "run",
+        "/app/modules/mesh-catalog/dist/index.js"
      ]
    }
-  ]
+  ],
+  "build": {
+    "artifacts": [
+      {
+        "name": "runtime",
+        "kind": "image",
+        "from": "Dockerfile"
+      }
+    ]
+  }
 }