[🐛 Bug]:

[lishidetainan]

What happened?

hello, I use the latest image selenium/standalone-chromium:latest and start the withe flollow :docker run -d -p 4444:4444 -p 7900:7900 --shm-size="2g" selenium/standalone-chromium:latest
but I can't access 4444 port what's wrong with me ?
I Use the os system: 4.19.90-83.0.v2307.ky10.aarch64

Command used to start Selenium Grid with Docker (or Kubernetes)

:docker run -d -p 4444:4444 -p 7900:7900 --shm-size="2g" selenium/standalone-chromium:latest

Relevant log output

can't access 4444

Operating System

4.19.90-83.0.v2307.ky10.aarch64

Docker Selenium version (image tag)

laetest

Selenium Grid chart version (chart version)

latest

[github-actions]

@lishidetainan, thank you for creating this issue. We will troubleshoot it as soon as we can.

---

Info for maintainers

Triage this issue by using labels.

If information is missing, add a helpful comment and then I-issue-template label.

If the issue is a question, add the I-question label.

If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted label.

If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C), add the applicable G-* label, and it will provide the correct link and auto-close the issue.

After troubleshooting the issue, please add the R-awaiting answer label.

Thank you!

[VietND96]

What is URL with port 4444 that you used?

[VietND96]

The same your command I used to reproduce on M1 (which has the same aarch64 as you), I can access http://localhost:4444/ui/

[VietND96]

If it still not working, copy all error logs from the container that you can see

[lishidetainan]

If it still not working, copy all error logs from the container that you can see

1.this is correct log, that can access 4444 with the standonly/chrome:
2024-12-04 10:38:17,077 INFO Included extra file "/etc/supervisor/conf.d/selenium.conf" during parsing
2024-12-04 10:38:17,081 INFO RPC interface 'supervisor' initialized
2024-12-04 10:38:17,081 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2024-12-04 10:38:17,081 INFO supervisord started with pid 8
2024-12-04 10:38:18,084 INFO spawned: 'xvfb' with pid 10
2024-12-04 10:38:18,085 INFO spawned: 'vnc' with pid 11
2024-12-04 10:38:18,087 INFO spawned: 'novnc' with pid 12
2024-12-04 10:38:18,089 INFO spawned: 'selenium-standalone' with pid 13
Setting up SE_NODE_GRID_URL...
2024-12-04 10:38:18,099 INFO success: xvfb entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2024-12-04 10:38:18,099 INFO success: vnc entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2024-12-04 10:38:18,099 INFO success: novnc entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2024-12-04 10:38:18,099 INFO success: selenium-standalone entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
Selenium Grid Standalone configuration:
[network]
relax-checks = true

[node]
session-timeout = "300"
override-max-sessions = false
detect-drivers = false
drain-after-session-count = 0
max-sessions = 1

[[node.driver-configuration]]
display-name = "chrome"
stereotype = '{"browserName": "chrome", "browserVersion": "110.0", "platformName": "Linux"}'
max-sessions = 1

Starting Selenium Grid Standalone...
Tracing is disabled
10:38:18.590 INFO [LoggingOptions.configureLogEncoding] - Using the system default encoding
10:38:18.595 INFO [OpenTelemetryTracer.createTracer] - Using OpenTelemetry for tracing
10:38:19.301 INFO [NodeOptions.getSessionFactories] - Detected 8 available processors
10:38:19.350 INFO [NodeOptions.report] - Adding chrome for {"browserVersion": "110.0","se:noVncPort": 7900,"browserName": "chrome","platformName": "LINUX","se:vncEnabled": true} 1 times
10:38:19.366 INFO [Node.] - Binding additional locator mechanisms: relative
10:38:19.387 INFO [GridModel.setAvailability] - Switching Node 750ec7e3-0caa-48bb-90ac-6ae781ed0852 (uri: http://172.17.0.2:4444) from DOWN to UP
10:38:19.388 INFO [LocalDistributor.add] - Added node 750ec7e3-0caa-48bb-90ac-6ae781ed0852 at http://172.17.0.2:4444. Health check every 120s
10:38:19.539 INFO [Standalone.execute] - Started Selenium Standalone 4.8.1 (revision 8ebccac989): http://172.17.0.2:4444

2. but when I use the image standalone-chromium:latest, the log as flollow, not the same with image standonly/chrome

2024-12-04 08:35:42,044 INFO Included extra file "/etc/supervisor/conf.d/chrome-cleanup.conf" during parsing
2024-12-04 08:35:42,045 INFO Included extra file "/etc/supervisor/conf.d/selenium.conf" during parsing
2024-12-04 08:35:42,059 INFO RPC interface 'supervisor' initialized
2024-12-04 08:35:42,060 INFO supervisord started with pid 9
2024-12-04 08:35:43,064 INFO spawned: 'xvfb' with pid 10
2024-12-04 08:35:43,073 INFO spawned: 'vnc' with pid 11
2024-12-04 08:35:43,078 INFO spawned: 'novnc' with pid 14
2024-12-04 08:35:43,088 INFO spawned: 'selenium-standalone' with pid 18
2024-12-04 08:35:43,098 INFO success: xvfb entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2024-12-04 08:35:43,098 INFO success: vnc entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2024-12-04 08:35:43,098 INFO success: novnc entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2024-12-04 08:35:43,098 INFO success: selenium-standalone entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)

[VietND96]

Via container logs, looks like server was started properly. Can you check further on host network to see anything is blocking access host port 4444 (which is container port exposed).

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.