ci: build harness-server from examples/Dockerfile.harness via ENTRY arg

The previous workflow pointed the harness-server matrix entry at
`deploy/fullstack-base/harness-server.Dockerfile` which only exists in the
enterprise-computeragent repo. CI failed with `resolve : lstat deploy: no
such file or directory`.

Fix: make examples/Dockerfile.harness parametric via an ENTRY build arg.
Same image layers; CMD picks between examples/harness-server.ts (bare
/v1/sessions route) and examples/computeragent-server.ts (full /run +
/sandboxes + /tasks). The CI matrix and build-and-push.sh now pass
--build-arg ENTRY=... per image.

Author: abhi-bhat-lyzr

.github/workflows/build-images.yml

@@ -44,12 +44,16 @@ jobs:
       fail-fast: false
       matrix:
         include:
+          # The two harness images share examples/Dockerfile.harness — only
+          # the entry script differs (ENTRY build arg).
           - name: harness-server
-            dockerfile: deploy/fullstack-base/harness-server.Dockerfile
-            build_args: ""
+            dockerfile: examples/Dockerfile.harness
+            entry: examples/harness-server.ts
+            build_args: harness
           - name: computeragent-server
             dockerfile: examples/Dockerfile.harness
-            build_args: ""
+            entry: examples/computeragent-server.ts
+            build_args: harness
           - name: agentos-server
             dockerfile: packages/agentos-server/Dockerfile
             build_args: ""
@@ -100,8 +104,8 @@ jobs:
           fi
           echo "tags=${TAGS}" >> "$GITHUB_OUTPUT"
 
-      - name: Build and push ${{ matrix.name }} (non-SPA)
-        if: matrix.build_args != 'spa'
+      - name: Build and push ${{ matrix.name }} (agentos-server)
+        if: matrix.build_args == ''
         uses: docker/build-push-action@v5
         with:
           context: .
@@ -111,6 +115,19 @@ jobs:
           cache-from: type=gha,scope=${{ matrix.name }}
           cache-to: type=gha,mode=max,scope=${{ matrix.name }}
 
+      - name: Build and push ${{ matrix.name }} (harness variant)
+        if: matrix.build_args == 'harness'
+        uses: docker/build-push-action@v5
+        with:
+          context: .
+          file: ${{ matrix.dockerfile }}
+          push: ${{ github.event_name != 'pull_request' }}
+          tags: ${{ steps.tags.outputs.tags }}
+          build-args: |
+            ENTRY=${{ matrix.entry }}
+          cache-from: type=gha,scope=${{ matrix.name }}
+          cache-to: type=gha,mode=max,scope=${{ matrix.name }}
+
       - name: Build and push agentos-spa (with VITE_ build args)
         if: matrix.build_args == 'spa'
         uses: docker/build-push-action@v5

examples/Dockerfile.harness

@@ -1,4 +1,15 @@
-# ComputerAgent harness — runs examples/computeragent-server.ts via bun.
+# ComputerAgent harness — runs one of the example server entries via bun.
+#
+# Defaults to examples/computeragent-server.ts (full harness: /run + /sandboxes
+# + /tasks + /snapshots, port 8787).
+#
+# Override the entry to build the BARE harness instead (just /v1/sessions/*
+# on port 7700), used by the Python qa-worker:
+#   docker build -f examples/Dockerfile.harness \
+#     --build-arg ENTRY=examples/harness-server.ts \
+#     -t harness-server .
+#
+# Same image layers in both cases — only the CMD differs.
 #
 # Build from the REPO ROOT so pnpm workspace resolution works:
 #   docker build -f examples/Dockerfile.harness -t computeragent-harness .
@@ -50,4 +61,11 @@ EXPOSE 8787
 # handles this).
 VOLUME ["/tmp/computeragent-sessions"]
 
-CMD ["bun", "run", "examples/computeragent-server.ts"]
+# Entry script — override at build time for the bare harness variant:
+#   --build-arg ENTRY=examples/harness-server.ts
+ARG ENTRY=examples/computeragent-server.ts
+ENV ENTRY=${ENTRY}
+
+# Shell form so $ENTRY is expanded at runtime by /bin/sh; `exec` keeps bun
+# as PID 1 (signals + Docker stop semantics still work).
+CMD exec bun run "$ENTRY"

scripts/build-and-push.sh

@@ -78,11 +78,14 @@ IFS=',' read -ra TARGETS <<< "${IMAGES}"
 for img in "${TARGETS[@]}"; do
   case "${img}" in
     harness-server)
+      # Bare harness — same Dockerfile, ENTRY override to harness-server.ts.
       build_one harness-server \
-        "${REPO_ROOT}/deploy/fullstack-base/harness-server.Dockerfile" \
-        "${REPO_ROOT}"
+        "${REPO_ROOT}/examples/Dockerfile.harness" \
+        "${REPO_ROOT}" \
+        --build-arg "ENTRY=examples/harness-server.ts"
       ;;
     computeragent-server)
+      # Default ENTRY in the Dockerfile already points at computeragent-server.ts.
       build_one computeragent-server \
         "${REPO_ROOT}/examples/Dockerfile.harness" \
         "${REPO_ROOT}"