Linux sandbox issues

Fixing Electron's SUID sandbox helper error when running or building AgentDock on Linux.

Warning

Linux support is experimental — there is no dedicated packaged-release smoke test, so this applies mainly when running or building AgentDock from source on Linux.

If Electron's sandbox helper isn't configured correctly, AgentDock fails to start on Linux with an error like:

text

FATAL:setuid_sandbox_host.cc(163)] The SUID sandbox helper binary was found,
but is not configured correctly.

AgentDock Pro

AgentDock Pro ships a Linux sandbox-permission fixer (npm run fix:sandbox) that isn't present in the free repository. It applies the correct ownership and permissions (chown root:root, chmod 4755) to Electron's chrome-sandbox helper via sudo.

How to fix it

Run the fixer script (Pro):

bash

npm run fix:sandbox

It only requests sudo when actually applying a fix — running it with a check-only flag won't invoke sudo unattended.

Important

AgentDock deliberately does not work around this by launching with --no-sandbox. Disabling the sandbox removes a real security boundary between the renderer process and your system — fix the sandbox helper's permissions instead of bypassing it.

If you're on the free (non-Pro) source tree and hit this, fix the chrome-sandbox binary's ownership and permissions manually, following Electron's own sandbox documentation, since the free repository doesn't include the automated fixer script.