Skip to content

Support Google Chrome 56 #383

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

Closed
wheleph opened this issue Feb 6, 2017 · 4 comments
Closed

Support Google Chrome 56 #383

wheleph opened this issue Feb 6, 2017 · 4 comments

Comments

@wheleph
Copy link
Contributor

wheleph commented Feb 6, 2017

This a potential issue that may complicate upgrade of Google Chrome within the images.

I tried to rebuild node-chrome image based on RHEL-like OS instead of Ubuntu. I noticed that Google Chrome crashed inside of the new image. It turned out that the problem is related to Google Chrome version 56 and is present in "official" images also (i. e. if you rebuilt the image today you would see the same issue because of the newer version of the browser).

Meta -

Image(s):
selenium/node-chrome
Docker Version:
1.12.3, build 6b644ec
OS:
Ubuntu 16.04

$ uname -a
Linux wheleph-laptop 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

Expected Behavior -

It's possible to upgrade Google Chrome to version 56 (the latest at the time of writing) inside selenium/node-chrome. The new version of the browser if fully functional.

Actual Behavior -

After the upgrade Google Chrome cannot be started. It crashes with the following error:

seluser@d5109fb59a5f:/$ google-chrome --version
Google Chrome 56.0.2924.87 
seluser@d5109fb59a5f:/$ google-chrome
Failed to move to new namespace: PID namespaces supported, Network namespace supported, but failed: errno = Operation not permitted
Illegal instruction (core dumped)
seluser@d5109fb59a5f:/$  
@ddavison
Copy link
Member

ddavison commented Feb 7, 2017

I believe this has been fixed, please try the new version and see if the problem persists.

@wheleph
Copy link
Contributor Author

wheleph commented Feb 8, 2017

The new version of node-chrome image contains Google Chrome 56 which works well. The issue seem to be related not to the browser itself but rather to the installation process.

If I take the image and remove Google Chrome via apt purge and reinstall it via apt install I still get the following:

seluser@cf37c71c54b0:/$google-chrome
Failed to move to new namespace: PID namespaces supported, Network namespace supported, but failed: errno = Operation not permitted
Illegal instruction (core dumped)
seluser@cf37c71c54b0:/$ google-chrome --version
Google Chrome 56.0.2924.87 

But there's no issues with the "official" image so this one can be closed. But if you have any idea why I get the error, please let me know.

@wheleph wheleph closed this as completed Feb 8, 2017
@elgalu
Copy link
Member

elgalu commented Feb 8, 2017

@wheleph I managed to solved the Failed to move to new namespace issue by using --no-sandbox

@wheleph
Copy link
Contributor Author

wheleph commented Feb 8, 2017

The original issue I had with RHEL-like systems was due to missing fonts. Here's the solution:

yum install liberation-mono-fonts liberation-narrow-fonts liberation-sans-fonts liberation-serif-fonts

See http://stackoverflow.com/questions/41641546/chrome-fails-with-illegal-instruction-in-minimal-centos7xvfb and https://www.centos.org/forums/viewtopic.php?f=48&t=60908&sid=6e5b5c743f897b9b300fe69bbae36337&start=10#p257122 for more details

@lock lock bot locked and limited conversation to collaborators Aug 14, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants