[🐛 Bug]: docker-selenium does not start correctly due to exit of novnc on openEuler #2438
Comments
|
@BlackManne, 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! |
BlackManne
changed the title
|
I saw pid novnc failed but don't have much info to understand what could be the issue |
|
I tried this method, here is the result: |
|
novnc exited as well, but the status turned from 1 to 0 |
|
Without novnc, selenium server can respond in your test? |
|
Stll, it cannot respond. Here is the Error Message: #invoke by http request: |
|
Can you try with image |
|
I already tried that...Still cannot work. Some outputs are listed as follows: docker exec -it selenium bashWarning: could not find self.pem seluser@887b879fb410:/$ /opt/bin/noVNC/utils/websockify/run main.py: error: Too few arguments |
|
What is docker version that you are using in your host? |
|
My docker version is: |
|
I think I found something and fixed. Deploying a preview image for your verification before publish the fix. Will inform you once done |
|
I noticed that this issue is closed. Should I get and use the latest image for solution？ |
|
Many thanks to you!!Looking forward to your message:) |
|
@BlackManne, can you use Nightly build |
|
It seems it doesn't work...and I got more errors when executing /opt/bin/noVNC/utils/websockify/run: main.py: error: Too few arguments |
|
And I got same errors as using tag "latest" when I execute following commands: docker exec -it selenium bashseluser@834a4954d3f0:/$ /opt/bin/start-novnc.sh docker logs selenium2024-10-25 04:56:16,539 INFO Included extra file "/etc/supervisor/conf.d/chrome-cleanup.conf" during parsing |
|
Ok, at least in recent change it solved this message
I suspect something relates to platform of your host also. Since I running the container on my devbox is Ubuntu 22.04, didn't see those error while container is running |
I feel sorry but maybe not? Because I still got this error message when executing "/opt/bin/start-novnc.sh". |
|
Can you try to start the container with both env vars SE_START_NO_VNC=false and SE_START_VNC=false |
|
Also, any options else set in your docker compose command? Or just simple |
I tried, here is the result: [root@DC4-73-003 sbom]# docker logs selenium |
just 'docker compose up -d' |
|
In your logs, is there nothing else after exit status 0? Here are logs that I could see docker run --rm -p 4444:4444 -e SE_ENABLE_TRACING=false -e SE_START_VNC=false -e SE_START_NO_VNC=false selenium/standalone-chromium:nightly |
|
No, there is nothing after exit status 0. It seems that the logs you've got is correct and my logs showed error... |
|
Openeuler is an aarch64 operating system. In fact I already tried docker-selenium on my ubuntu, no error occured and everthing went well. That's the most confusing point for me :( |
|
In host using |
What happened?
I tried to launch a docker-selenium container on an openEuler machine. The selenium service is a part of a python project of 4 containers, including main container(called sbom), elasticsearch, mongodb and selenium. The selenium service seems to run correctly because it can be shown by command "docker ps", but when I try to invoke it by http request, an error occurs(message: connection refused) . And when I execute "docker exec selenium curl http://localhost:4444/wd/hub/status", it fails either.
Command used to start Selenium Grid with Docker (or Kubernetes)
Relevant log output
Operating System
openEuler 22.03 LTS for ARM
Docker Selenium version (image tag)
125.0
Selenium Grid chart version (chart version)
No response
The text was updated successfully, but these errors were encountered: