Closed philjones88 closed 7 years ago
@philjones88 I wasn't able to replicate your issue. I'm using the latest beta
version (beta32). See below my environment details:
docker-compose.yml
version: '2'
services:
nodejs:
container_name: nodejs
image: node:4
ports:
- "9001:9000"
volumes:
- ./:/tests
working_dir: /tests
depends_on:
- selenium_hub
- nodechrome
command: "node /tests/node_modules/protractor/bin/protractor /tests/conf.js"
networks:
- selenium_grid_internal
selenium_hub:
image: selenium/hub:3.0.1-aluminum
container_name: selenium_hub
privileged: true
ports:
- 4444:4444
environment:
- GRID_TIMEOUT=120000
- GRID_BROWSER_TIMEOUT=120000
networks:
- selenium_grid_internal
nodechrome:
image: selenium/node-chrome-debug:3.0.1-aluminum
privileged: true
depends_on:
- selenium_hub
ports:
- 5900
environment:
- no_proxy=localhost
- TZ=Europe/London
- HUB_PORT_4444_TCP_ADDR=selenium_hub
- HUB_PORT_4444_TCP_PORT=4444
networks:
- selenium_grid_internal
networks:
selenium_grid_internal:
config.js
// An example configuration file.
exports.config = {
seleniumAddress: 'http://selenium_hub:4444/wd/hub',
// Capabilities to be passed to the webdriver instance.
capabilities: {
'browserName': 'chrome'
},
// Framework to use. Jasmine is recommended.
framework: 'jasmine',
// Spec patterns are relative to the current working directory when
// protractor is called.
specs: ['example_spec.js'],
// Options to be passed to Jasmine.
jasmineNodeOpts: {
defaultTimeoutInterval: 30000
}
};
package.json
{
"dependencies": {
"protractor": "*"
},
"scripts": {},
"devDependencies": {
"protractor": "*"
}
}
Can you please try it again with that?
I should add it can happen after 1 suite of tests, even 1 test.
I'm on vacation at the moment but when I return next week I will try your docker file.
I've just upgraded to beta 32, the report was filed under beta 31, so fingers crossed it was magically fixed.
This issue has been inactive for more than 14 days while marked as status/0-more-info-needed
. It is being closed due to abandonment. Please feel free to re-open with more information about the problem.
MORE_INFO_EXPIRY_TIMEOUT
@philjones88 Hi, sorry to comment on a closed issue but I don't know how else to contact you. Have you been able to solve your issue? I have the same exact problem (same stacktrace), happens only with containerized chrome (either with selenium, or native chromedriver+chrome or chromium). Firefox runs perfectly. I tried switching back from edge to 17.03-ce stable, same result. My VM has always worked with 3GB of ram but the memory usage doesn't seem to be an issue: I increased it to 8GB and I get the same crash at mostly the same time.
@asprega sorry, I never really resolved it, just swapped to Protractor's web driver manager stuff instead which doesn't use docker :(
Closed issues are locked after 30 days of inactivity. This helps our team focus on active issues.
If you have found a problem that seems similar to this, please open a new issue.
Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. /lifecycle locked
Expected behavior
To not crash. Running SeleniumHQ selenium-hub and node-chrome-debug images.
https://github.com/SeleniumHQ/docker-selenium
Actual behavior
Crashes.
Information
B61E99DF-82FC-4705-93F7-D5CBE45C367D
Compose file:
docker-compose up -d
Run something that uses a selenium grid. Protractor etc.
Steps to reproduce the behavior
See above.