ci: run on host instead of a container

Containerized jobs on this act_runner fail during setup: the runner extracts its payload to /var/run/act, /var/run is a symlink to /run in the Debian job image, and Docker's archive extractor refuses to write through it ("path escapes from parent"). CI had never passed as a result -- 19 runs, 19 failures, including the v0.5.0 release commit. Every other repo on this runner already uses `runs-on: host`. ui-kit builds no image and deploys nothing, so container isolation buys it nothing. Refs #6 Co-Authored-By: Claude Opus 5 <[email protected]>
2026-08-24 22:47:09 -05:00
parent efc2238802
commit 1dc64c7c13
1 changed files with 7 additions and 1 deletions
@@ -6,7 +6,13 @@ on:

 jobs:
  build-and-design:
-    runs-on: ubuntu-latest
+    # `host`, not `ubuntu-latest`. A containerized job on this act_runner dies
+    # during setup with `mkdirat var/run/act: path escapes from parent` — the
+    # runner extracts its payload to /var/run/act, and /var/run is a symlink to
+    # /run in the Debian/Ubuntu job images, which Docker's archive extractor
+    # refuses to write through. See #6. ui-kit ships no image and deploys
+    # nothing, so there is nothing to isolate; the job just needs Node + repo.
+    runs-on: host
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4