charmbracelet / charmbracelet/vhs

VHS_NO_SANDBOX ENV option needs documented

Open Beginner friendly
#504 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Go
Stars
20.9k
Forks
480
Avg merge
4d 1h
Merged PRs (30d)
2

Description

After banging my head against the wall on the on this error:

could not launch browser: [launcher] Failed to get the debug url: [0719/182133.729582:FATAL:zygote_host_impl_linux.cc(127)]
No usable sandbox! Update your kernel or see https://chromium.googlesource.com/chromium/src/+/main/docs/linux/suid_sandbox_development.md 
for more information on developing with the SUID sandbox. If you want to live dangerously and need an 
immediate workaround, you can try using --no-sandbox.

I came across https://github.com/charmbracelet/vhs/issues/45 which is referenced by https://github.com/charmbracelet/vhs/pull/195 which was merged over 2 years ago, and added VHS_NO_SANDBOX but doesn't seem to be documented anywhere outside of that PR.

For server mode, env options are documented in the readme ( https://github.com/charmbracelet/vhs/blob/main/README.md#the-vhs-server )...

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in README.md at the “The VHS server” section, where server-mode environment options are documented. Add documentation for the VHS_NO_SANDBOX environment option, then check that the README clearly explains its availability and purpose.

Written by the indexing model from the issue text.

Assessment

Domain
cli, documentation
Issue type
Documentation
Difficulty
1/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
72/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.