LinusU / LinusU/upload-opera-extension
Disabling puppeteer sandbox for linux machines
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 8
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
I just tried to use your package to deploy from my linux server and it failed to start chrome:
> Error! Error: Failed to launch chrome!
[0520/024527.811997:FATAL:zygote_host_impl_linux.cc(126)] No usable sandbox! Update your kernel or see https://chromium.googlesource.com/chromium/src/+/master/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.
According to [the puppeteer troubleshooting guide](https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md#chrome-headless-fails-due-to-sandbox-issues) this problem can be prevented by disabling sandbox.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no repository file or test; start by locating where Chrome or Puppeteer is launched and review the linked Puppeteer sandbox guidance. Confirm the deployment works on a Linux server with the sandbox disabled, while preserving the package's existing upload behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, linux
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100