[🐛 Bug]: NODE_MAX_SESSION and NODE_MAX_INSTANCES variables are ignored

[dimaklepikov]

What happened?

I try to scale up a concurrent session amount using your image. Now, it's impossible to run more than one session (depends on CPUs count). Is there a way to do it?

Command used to start Selenium Grid with Docker

docker run -e NODE_MAX_INSTANCES=5 -e NODE_MAX_SESSION=5 --rm -it -p 4444:4444 -p 5900:5900 -p 7900:7900 --shm-size 2g seleniarm/standalone-chromium:latest

Relevant log output

[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": "114.0", "platformName": "Linux"}'
max-sessions = 1

Starting Selenium Grid Standalone...
Tracing is disabled
18:55:10.577 INFO [LoggingOptions.configureLogEncoding] - Using the system default encoding
18:55:10.587 INFO [OpenTelemetryTracer.createTracer] - Using OpenTelemetry for tracing
18:55:11.548 INFO [NodeOptions.getSessionFactories] - Detected 1 available processors
18:55:11.601 INFO [NodeOptions.report] - Adding chrome for {"browserName": "chrome","browserVersion": "114.0","platformName": "linux","se:noVncPort": 7900,"se:vncEnabled": true} 1 times (Host)
18:55:11.619 INFO [Node.<init>] - Binding additional locator mechanisms: relative
18:55:11.649 INFO [GridModel.setAvailability] - Switching Node 62a98bec-05f4-49e7-88ff-f17eedb0541f (uri: http://172.17.0.2:4444) from DOWN to UP
18:55:11.650 INFO [LocalDistributor.add] - Added node 62a98bec-05f4-49e7-88ff-f17eedb0541f at http://172.17.0.2:4444. Health check every 120s
18:55:11.843 INFO [Standalone.execute] - Started Selenium Standalone 4.10.0 (revision c14d967899): http://172.17.0.2:444

Operating System

macOS 13.4.1

Docker Selenium version (tag)

latest

[diemol]

You can always check the docs https://github.com/seleniumhq-community/docker-seleniarm#increasing-session-concurrency-per-container

[github-actions[bot]]

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.