-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Chrome won't work without --no-sandbox option #149
Comments
Oh it's because you don't have userns enabled in your kernel |
See #65 |
I can confirm after enabling User Namespace and re-compiling the kernel (4.7RC3), it works flawlessly. Also, VLC on docker seems to be working better and i3 shows the logo at the bottom. |
I got the same problem ,so i disable sandbox ,but it still cann't works! |
@creatist You need to enable user namespaces in your kernel for this to work. |
Could you tell me what command you ran to do this? I'm new to docker. |
did you get any resources for how to disable sandbox and run chrome in docker. |
Yes, please help! I'm totally lost reading pages like this: |
Hi !
I'm using Arch as host, with 4.6.2-1 kernel and 1.11.2 is my Docker version.
This doesn't work for me:
this doesn't open the chrome window for me. but when I add
--no-sandbox
or--disable-setuid-sandbox
, it works.Also, with 512mb ram, it crashes tabs multiple times, also "HTTPS everywhere" and "uBlock" will crash multiple times. adding
--disable-appcontainer
won't help either.is there any way to run Chrome container with sand-boxing in Arch ?
best regards.
The text was updated successfully, but these errors were encountered: