You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Grok lanes fail on studio1: the sandbox refuses OrbStack's /var/run/docker.sock symlink #275
Every Grok lane on studio1 fails at sandbox start, so Grok drops out of every panel there (the default interrogate and arena panels included).
Observed 2026-11-06 during PR #271's live gate (setup keep-predecessor case): the grok:grok-4.6@high probe passed login and model checks, then Grok 1.0.77 refused to start its read-only sandbox because /var/run/docker.sock is a symlink to ~/.orbstack/run/docker.sock, and its sandbox cannot add a symlink that points outside its block list. pstack correctly stopped instead of running Grok unprotected. pro14 has no /var/run/docker.sock and its Grok lanes run.
Acceptance:
The cause is reproduced directly with grok on studio1 and pinned to a Grok version and host setting.
Grok lanes run on studio1 with their bounded sandbox intact: no devbox or off sandbox, no runner change that weakens the read-only or workspace profile (provider-dispatch.md Host and parent prerequisites).
If the fix is a host setting, Grok's catalog note under Host prerequisites names it, so setup's probe failure points at it.
Reproduced with grok -p … --sandbox read-only: "socket deny resolution failed: could not resolve runtime-socket deny path /var/run/docker.sock: endpoint is a symlink to a path outside the deny list", then "Refusing to start with its protections missing."
Grok's built-in runtime-socket list (from the binary): /var/run/docker.sock, /run/podman/podman.sock, /var/run/podman/podman.sock, /run/containerd/containerd.sock, /var/run/containerd/containerd.sock, ~/.docker/desktop/docker.sock, ~/.docker/run/docker.sock. A listed endpoint that is a symlink must point inside that list. OrbStack's /var/run/docker.sock points to ~/.orbstack/run/docker.sock, which is not listed.
~/.grok/sandbox.toml cannot fix it: a custom profile extending read-only with deny = ["~/.orbstack/run/docker.sock"], and an override of [profiles.read-only] with the same deny, both fail the same way.
docker on studio1 uses the orbstack context (unix:///Users/ericlitman/.orbstack/run/docker.sock), not /var/run/docker.sock; DOCKER_HOST is unset. pro14 has no /var/run/docker.sock, and its Grok lanes run.
So the gap is in Grok (OrbStack's socket missing from its list). The host-side workaround is to stop OrbStack creating the /var/run/docker.sock link.
Host fix applied on studio1, 2026-11-06 (Eric's choice: drop the link). Removed the symlink /var/run/docker.sock (sudo rm on the link only; OrbStack's socket ~/.orbstack/run/docker.sock is untouched). docker ps still works through the orbstack context.
Checked after: grok -p … --sandbox read-only --model grok-4.7 returned the requested text, and pstack-runner --provider grok --model grok-4.7 --effort low --mode read-only gave a complete receipt.
Left: OrbStack's setup.use_admin: true may recreate the link when OrbStack restarts. Grok's catalog note gets one host-prerequisite line naming this cause, in the same PR as #269 (both regenerate the catalog).
All three acceptance points hold: reproduced and pinned to Grok 1.0.77 and OrbStack's /var/run/docker.sock link; Grok lanes run on studio1 with the bounded sandbox after removing the link (2026-11-06); Grok's catalog host prerequisite and note shipped in #276 (Open Pstack 1.20.0). If OrbStack restarts and recreates the link, the note says what to do.
Reproduced and pinned: done. Grok 1.0.77's sandbox has a fixed runtime-socket list; OrbStack's /var/run/docker.sock links to ~/.orbstack/run/docker.sock, which is not on it; sandbox.toml deny entries do not help (tested).
Grok runs on studio1 with the bounded sandbox: done. Eric chose "Drop the link (Recommended)" and wrote "you have sudoers permission on studio1, make the change yourself". I removed only the symlink; grok --sandbox read-only and a runner Grok lane completed (checked directly, not through a live gate). OrbStack's setup.use_admin may recreate the link on restart.
Activity
ericlitman commentedon Nov 6, 2026
Findings, 2026-11-06 (studio1, Grok 1.0.77, OrbStack 2.2.5):
grok -p … --sandbox read-only: "socket deny resolution failed: could not resolve runtime-socket deny path /var/run/docker.sock: endpoint is a symlink to a path outside the deny list", then "Refusing to start with its protections missing."/var/run/docker.sock,/run/podman/podman.sock,/var/run/podman/podman.sock,/run/containerd/containerd.sock,/var/run/containerd/containerd.sock,~/.docker/desktop/docker.sock,~/.docker/run/docker.sock. A listed endpoint that is a symlink must point inside that list. OrbStack's/var/run/docker.sockpoints to~/.orbstack/run/docker.sock, which is not listed.~/.grok/sandbox.tomlcannot fix it: a custom profile extendingread-onlywithdeny = ["~/.orbstack/run/docker.sock"], and an override of[profiles.read-only]with the same deny, both fail the same way.dockeron studio1 uses theorbstackcontext (unix:///Users/ericlitman/.orbstack/run/docker.sock), not/var/run/docker.sock;DOCKER_HOSTis unset. pro14 has no/var/run/docker.sock, and its Grok lanes run.So the gap is in Grok (OrbStack's socket missing from its list). The host-side workaround is to stop OrbStack creating the
/var/run/docker.socklink.ericlitman commentedon Nov 6, 2026
Host fix applied on studio1, 2026-11-06 (Eric's choice: drop the link). Removed the symlink
/var/run/docker.sock(sudo rmon the link only; OrbStack's socket~/.orbstack/run/docker.sockis untouched).docker psstill works through theorbstackcontext.Checked after:
grok -p … --sandbox read-only --model grok-4.7returned the requested text, andpstack-runner --provider grok --model grok-4.7 --effort low --mode read-onlygave acompletereceipt.Left: OrbStack's
setup.use_admin: truemay recreate the link when OrbStack restarts. Grok's catalog note gets one host-prerequisite line naming this cause, in the same PR as #269 (both regenerate the catalog).docs(catalog): note Amp's writer hang and Grok's OrbStack socket prer…
ericlitman commentedon Nov 6, 2026
All three acceptance points hold: reproduced and pinned to Grok 1.0.77 and OrbStack's /var/run/docker.sock link; Grok lanes run on studio1 with the bounded sandbox after removing the link (2026-11-06); Grok's catalog host prerequisite and note shipped in #276 (Open Pstack 1.20.0). If OrbStack restarts and recreates the link, the note says what to do.
ericlitman commentedon Nov 6, 2026
Batch 262 closeout for this issue (full record: https://github.com/mobilyze-llc/docs/blob/main/projects/open-pstack/records/2026-11-06-batch-262/closeout.md):
#275: Grok lanes fail on studio1
/var/run/docker.socklinks to~/.orbstack/run/docker.sock, which is not on it;sandbox.tomldeny entries do not help (tested).grok --sandbox read-onlyand a runner Grok lane completed (checked directly, not through a live gate). OrbStack'ssetup.use_adminmay recreate the link on restart.