electron: electron@5.0.0-beta.1 fails with error: No usable sandbox!

electron: 5.0.0-beta.1 platform: linux x64

Actual behavior

https://github.com/electron/electron-quick-start app fails to start with the following error:

[3937:0131/003107.790938:FATAL:zygote_host_impl_linux.cc(116)] 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.

To Reproduce

git clone https://github.com/electron/electron-quick-start.git
cd electron-quick-start
npm install
npm add --only=dev electron@5.0.0-beta.1
any of the following commands fail:
- npm start
- node_modules/.bin/electron --version

Additional Information

Worth to mention that event just node_modules/.bin/electron --version execution fails with the same error.

CC @nornagon

About this issue

Original URL
State: closed
Created 5 years ago
Reactions: 1
Comments: 15 (7 by maintainers)

Most upvoted comments

Arch Linux and distributives based on it are quite popular on desktop and electron@5.0.0-beta.1 fails there since user namespaces sandboxing is forced. User namespaces sandboxing can only be enabled on those systems by manual kernel.unprivileged_userns_clone option tweaking (root/sudo access rights required). So I’d imagine electron to try user namespaces sandbox first and fallback to setuid sandbox if the primary option is unsupported by the system.

vladimiry on Jan 31, 2019