Google Chrome 75.0.3770.80 HEADLESS no longer works inside Docker container
See original GitHub issueThis was originally reported as https://github.com/karma-runner/karma/issues/3328 but the Karma team asked it be reported here instead.
In short, Chrome 74 headless worked flawless with karma-chrome-launcher from inside a Docker container but when Chrome 75 releases karma can no longer connect. Several folks with otherwise valid configuration starting hitting this bug shortly after Chrome 75 was released.
For completeness, here is the launcher configuration being used (but as I said, the only thing that changed between working/not working was Chrome version
customLaunchers: {
ChromeDocker: {
base: 'ChromeHeadless',
flags: [
'--no-sandbox'
]
}
},
Issue Analytics
- State:
- Created 4 years ago
- Reactions:18
- Comments:12
Top Results From Across the Web
Unable to open Google Chrome browser on Docker container
Google Chrome 75.0.3770.80 is installed on Docker image on CentOS 7. Chrome driver 75.0.3770.80 is checked-in with the framework.
Read more >How to use Puppeteer inside a Docker container
The easiest path to use Puppeteer inside a Docker container is installing Google Chrome because, in contrast to the Chromium package offered ...
Read more >regrex in Selenium IDE (Google Chrome extension) did not work
I tried to verify text with regrex in Selenium IDE (Google Chrome extension), but it's not working, although I follow step by step...
Read more >How to Install Google Chrome on RHEL 8 - Tecmint
Note: Google Chrome's support for 32-bit Linux distros ended in March 2016 and it no longer supports RHEL 6.X so update your distro...
Read more >selenium.common.exceptions.invalidargumentexception ...
This if 'ontouchmove' in iframe will not work since iframe here is a web element, ... Message: invalid argument (Session info: headless chrome=87.0.4280.88)....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Using the
--disable-dev-shm-usage
flag fixed this for me.Thanks for reporting @mramato
I’ll have a look at it as soon as possible.