Lost UI Shared context about docker-node-karma-protractor-chrome HOT 4 CLOSED

Try adding --remote-debugging-port=9222, without a remote debugging port, chromium doesn't start in headless mode.
These errors appeared in chromium 64, chromium 63 have none of these, it doesn't seem to block karma or protractor from running.

from docker-node-karma-protractor-chrome.

Thanks, that clears it up and I could get it working now!

from docker-node-karma-protractor-chrome.

Once I added --remote-debugging-port=9222, error is gone, but now chrome will not start. Please, help. I get the following:

Starting b03 08 2018 18:43:53.152:WARN [launcher]: Chrome have not captured in 60000 ms, killing.

I am at version: Google Chrome 64.0.3282.186

from docker-node-karma-protractor-chrome.

@mohyeid you can learn more about this error in puppeteer/puppeteer#1925, but it is not a fatal error and you don't have to worry about it.
Chrome have not captured in 60000 ms, killing. could mean chrome doesn't start, or karma can't connect to it. If I remember correctly, setting --remote-debugging-port in chrome flags makes karma unable to connect to it.
Try just removing --remote-debugging-port=9222 from your karma flags and everything should be working fine.
--remote-debugging-port=9222 is required to keep chrome running only when launched manually.

from docker-node-karma-protractor-chrome.