-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[🐛 Bug]: Chrome docker tags 124.0 / 4.20 SessionNotCreatedException #2225
Comments
@kisuro, thank you for creating this issue. We will troubleshoot it as soon as we can. Info for maintainersTriage this issue by using labels.
If information is missing, add a helpful comment and then
If the issue is a question, add the
If the issue is valid but there is no time to troubleshoot it, consider adding the
If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C),
add the applicable
After troubleshooting the issue, please add the Thank you! |
Can you provide the test to reproduce and what binding version is used? Since our CI tests not seen this failure |
docker:20.10.12-dind I use pytest for tests, with fixtures, objects, etc, but the problem is that all 100 tests crashed with this error without even starting, the browser was not initialised. Also tried a local run with selenium 4.20 on Chrome 124.0 - all runs successfully. |
I guess there is lib using HTTP/1.1 and it isn't compatible to be proceeded by selenium as the message |
@diemol, this case is Python binding. Do you have any idea how to troubleshoot? |
example simple test:
error log (selenium/standalone-chrome:latest):
successful log (just updated tag: selenium/standalone-chrome:123.0):
|
What version of Selenium Python? |
now updated to 4.20.0, was 4.19.0 . |
@kisuro, can you try to start the container with set |
pre:
Result log:
|
@kisuro, is this issue able to reproduce with the recent |
Yes, its still reproduce. log:
image: docker:20.10.9 d.compose not in use. stage: test |
I feel the issue could be with Docker engine |
Was updated image docker version:
But result the same: as I can see:
|
@kisuro Perhaps you found a way to solve this problem and could share? |
No. I still have this problem with last version, still using 123.0.6312.86 and hope someone from team help me resolve it |
@VietND96, @diemol any update, idea? logs
|
What if you deploy Hub container with env var set |
docker:20.10.24 and added SE_JAVA_OPTS
LOG:
|
Can you also try to use image tag |
Same result. gitlab-ci.yml
LOG
|
Ok, how about all the capabilities that you set from binding while creating the RemoteWebDriver? |
|
I feel it could be one of those caps that caused the browser not started properly. To confirm this, can you try a sample run without any options set? |
Was removed all options except: opt.add_argument("--headless=new") |
@kisuro, can you check the latest image tag |
Changed Selenium version (requirements.txt): updated gitlab-ci.yml lines:
Result the same :(
|
@kisuro I also encountered a similar issue when I set |
I still have this problem... Cant find any solution for fix the problem |
selenium 4.25.0 (python) `conftest.py:301: framework/application.py:88: in init self = <selenium.webdriver.remote.errorhandler.ErrorHandler object at 0x7faf853d8c50>
E selenium.common.exceptions.SessionNotCreatedException: Message: Could not start a new session. No nodes support the capabilities in the request |
In your test, any steps |
For test was removed all Also not used grid "fully" just as service(.gitlab-ci.yml):
|
I created a simple reproduce with all options you mentioned reproduce.txt (rename .txt to .py), but could not reproduce. So, you can update this file and send back to us docker run -p 4444:4444 selenium/standalone-chrome:nightly
|
Good afternoon @VietND96, thank you very much for your reply!
in this configuration everything is reproduced.
I will be very grateful for your help. Ps. left only two lines in requirements.txt: application.txt |
What happened?
I use selenium as a service in gitlab-ci.yml (selenium/standalone-chrome:latest)
Before the current update this morning, everything was fine.
However, after tag updates to 4.20 and 124 this morning, I started getting an error on all environments
Tried updating selenium to 4.20,
tried tags :
selenium/standalone-chrome:124.0
selenium/standalone-chrome:latest
selenium/standalone-chrome:4.20
All of these options return the Message: Failed to start a new session
When setting tag 123.0 (selenium/standalone-chrome:123.0) everything works correctly.
Command used to start Selenium Grid with Docker (or Kubernetes)
Relevant log output
Operating System
Linux
Docker Selenium version (image tag)
latest
Selenium Grid chart version (chart version)
No response
The text was updated successfully, but these errors were encountered: