This repository has been archived by the owner on Sep 16, 2021. It is now read-only.
Disable Chrome sandbox when unavailable #306
Merged
+37
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Chrome on Linux uses sandboxing, which needs user namespaces to be enabled.
This is not available on all kernels and it might be turned off even if it is available.
Notable examples where user namespaces are not available include:
We can detect if user namespaces are supported via /proc/sys/kernel/unprivileged_userns_clone.
For more information see:
puppeteer/puppeteer#290
https://superuser.com/questions/1094597/enable-user-namespaces-in-debian-kernel#1122977
karma-runner/karma-chrome-launcher#158
angular/angular#24906