mikejohnstonPremierinc

Encountering this same issue with version 122 standalone chrome/edge/firefox and with node-docker 4.18.1 and hub 4.18.1 > version: "3" services: node-docker: image: selenium/node-docker:4.18.1 volumes: - /share/pqafiles/assets:/opt/selenium/assets - /share/pqafiles/config/toml_server1.toml:/opt/bin/config.toml - /var/run/docker.sock:/var/run/docker.sock...

@VietND96 I am unable to test 4.19.0 because it is throwing the error below. nnode-docker does not get created successfully ``` Attaching to node-docker-1, selenium-hub selenium-hub | 2024-03-28 13:14:33,965 INFO...

> I've made a fix where I'm fairly sure that is related to this. Just to be certain, can you try running with `--ulimit nofile=65536:65536` to see if that makes...

> @mikejohnstonPremierinc I have only used the standalone images myself and am not knowledgeable how that plays with the individual instances. Can you apply the additional config to `node-docker`? I'm...

I apologize. It actually IS fixed for me now with version 4.20. I have deleted my posts above about it not being fixed in 4.20.

> Does this happen on the latest version of the image? Yes it does