-
-
Notifications
You must be signed in to change notification settings - Fork 53
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
Driver isn't created when using @DockerBrowser with browser type "CHROME" on macOS. #238
Comments
I have just made some quick test and it seems working, at least when using Windows or Linux. I don't have a macOS to test it. To discover the problem, I would need to see your Selenium-Jupiter traces. I mean something like this:
|
Hi. Thank you for quick response. |
For getting the Selenium-Jupiter logs, you need to include a Logback configuration file (for example, like this) in your project classpath. The name of this file should be After that, when running a test, you should see the traces as described before. For further info about logging with with SLF4J and Logback you can see the following tutorial. |
Ah, thank you. Now I get logs:
And here what displays after redirecting to
|
Not sure about VNC, but the driver instance seems to be properly created. |
If it had been created, then driver wouldn't be null I guess. Despite the logs show that WebDriver object is created, actually after redirecting with that URL error message is shown which I pasted in my previous comment: For browser type of FIREFOX noVNC URL is generated successfully and the Webdriver object is created at this URL properly, because code gets executed successfully. |
It seems the Docker container with the browser cannot be started. I don't know what the problem is, and unfortunately, I don't have a Mac to test with. If you want, you can try the following alternatives to try to discover the problem:
Then, you should be able to connect with the browser, for example checking the following URL:
Then, run the test again, and copy the traces here. Thank you. |
Thank you for response.
And so on ... the mentioned part in logs is repetitive. |
As I temporary fix, you can try to include this logic in your test class:
If this works, I put it in the next release of Selenium-Jupiter. Please let me know the result. |
Included in the test class. Same result.
Please let me know if they are more possible options for bypassing the problem. I'll try them all :) |
Please try this (I read the order of parameter might be important):
If this does not work, please try this:
Please let me know the result. |
Hi. I think I have gotten new updates. It shows this message after redirecting to localhost:4444/status But after the removal of So it's most probably not a Selenium-Jupiter related issue. |
I don't know, maybe you can try with even more shared memory:
... or in your test:
|
Again no success :/ |
More precisely, it is related to: |
Seems that's already ready :) I'd like to kindly ask if it's possible to fix Selenium's images? thanks a lot ;) |
I'm not able to run a test when docker browser type is set to CHROME:
When I set the Browser type to chrome, driver isn't being initialized and after first usage of driver NullPointerException appears, as the driver is null.
Browser and version: Chrome in docker - chrome_99.0
Operating system: macOS Monterey 12.3, chip - Apple M1 Pro
Selenium-Jupiter version: Currently, the latest version - 4.1.0
Selenium-Jupiter use:
Error trace:
NOTE:
I'm not 100% sure that this is an exact selenium-jupiter problem, but when specifying type FIREFOX, driver gets created successfully. And also plus, after setting "vnc" to true still there is no noVNC URL generated.
The text was updated successfully, but these errors were encountered: