Fix missing workspace when herald run in container

2026-09-20 13:10:05 +00:00
parent 620ec6727e
commit 48e09aa373
7 changed files with 81 additions and 29 deletions
@@ -61,6 +61,18 @@ Herald drives the container daemon through its socket: `DOCKER_HOST` (default
 Docker-compatible socket. The repository must contain a
 `.devcontainer/devcontainer.json`.

+Herald can therefore run inside a container with only that socket mounted (no
+shared workspace directory is required): the clone is streamed to the daemon over
+the socket, like the build context, instead of being bind-mounted from a host
+path the daemon would have to see. This is the setup the `Containerfile`
+produces, e.g.:
+
+```sh
+podman run --env-file=.env -p 3001:3001 \
+    -v /run/user/$(id -u)/podman/podman.sock:/var/run/docker.sock \
+    herald:latest
+```
+
 The `runArgs` of that file are read but deliberately **not** passed to the daemon:
 they come from an untrusted pull request, and one of them (`--network host`) would
 attach the container to another network and quietly