From 25d7de26b369f827fe5b8fcb634e1410d4102c15 Mon Sep 17 00:00:00 2001 From: Meta Vens Date: Thu, 17 Sep 2026 02:09:12 +0200 Subject: [PATCH] Point the container recipe at whatever checkout is running it The mount was this machine's own path, so the one documented way to build and check the Linux bridge needed editing before it would run anywhere else. It is the repository root now, named as the shell names it. Co-Authored-By: Claude Opus 5 --- native/GameCult.Mesh.Quic.Native/README.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/native/GameCult.Mesh.Quic.Native/README.md b/native/GameCult.Mesh.Quic.Native/README.md index 4653f86c..92041e8d 100644 --- a/native/GameCult.Mesh.Quic.Native/README.md +++ b/native/GameCult.Mesh.Quic.Native/README.md @@ -110,9 +110,12 @@ mutation harness that drives the runtime-lifetime scenarios is a Node script and a container that cannot run it cannot check the bridge it just built: docker build -t cultlib-quic-native-dev -f scripts/quic-native-linux-dev.Dockerfile scripts - docker run --rm --security-opt seccomp=unconfined -v F:\Projects\CultLib:/src -w /src \ + docker run --rm --security-opt seccomp=unconfined -v "${PWD}:/src" -w /src ` cultlib-quic-native-dev bash -lc "scripts/build-quic-native.sh && node scripts/mutate-cultmesh.mjs native" +Both lines are run from the repository root, and the mount is that root wherever +it is: `${PWD}` in PowerShell, `$(pwd)` in a POSIX shell. + `--security-opt seccomp=unconfined` is load-bearing, not caution. The ThreadSanitizer configuration needs the process's address space where it expects it, so `scripts/mutate-cultmesh.mjs` re-executes those runs under `setarch -R`,