Skip to content

Commit 596404f

Browse files
docs(browser): clarify sandbox setup for configured executables
1 parent f5466dc commit 596404f

1 file changed

Lines changed: 9 additions & 1 deletion

File tree

‎docs/user/remote-access.md‎

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -286,7 +286,15 @@ This also applies to HTML previews. T3 Code does not download or update that bro
286286
you maintain its Playwright compatibility, libraries, and security updates. An empty,
287287
relative, missing, or non-executable path fails without falling back to a download.
288288

289-
macOS, Windows, and Linux desktops run the browser as is. Some Linux hosts need
289+
The configured browser also needs its own working sandbox. On Linux hosts that
290+
restrict user namespaces, its package must supply a usable sandbox helper or an
291+
AppArmor profile permitting user namespaces for that executable's actual path.
292+
See [Chromium's sandbox guidance](https://chromium.googlesource.com/chromium/src/+/main/docs/security/apparmor-userns-restrictions.md).
293+
`t3 browser setup` configures only T3's managed browser path; its success message
294+
and the managed-profile startup check do not establish that a configured browser
295+
can launch. Follow the configured browser package's sandbox setup instructions.
296+
297+
For T3's default managed browser, macOS, Windows, and Linux desktops run it as is. Some Linux hosts need
290298
one-time setup: Ubuntu 23.10 and later block the sandbox the browser runs in,
291299
and minimal images and containers lack libraries it loads. When that happens,
292300
the server says so at startup, and browser tabs and HTML previews show the

0 commit comments

Comments
 (0)