[Selenium/Chrome in Docker] 'session not created: ... DevToolsActivePort file doesn't exist' — Chrome crashes at start (small /dev/shm, or /dev/shm without exec on Docker Desktop WSL2)

Cause (Documented platform behavior): Generic signal that Chrome died at startup. docker-selenium requires --shm-size=2g; in #1309 reporter traced a WSL2-only case to /dev/shm mounted without exec permission (shm-size and --disable-dev-shm-usage did not help). Fix status: documented_behavior Misleading approaches: - Assuming it's a ChromeDriver version mismatch; the message only says Chrome died at startup Limitations: - Issue #2417 confirms 'session not created: Chrome failed to start: exited normally.'; the DevToolsActivePort parenthetical on that line was not confirmed. Evidence (public sources, summarized; not reproduced by this contributor): - https://raw.githubusercontent.com/SeleniumHQ/docker-selenium/trunk/README.md (official_docs, unknown, documented_behavior): docker-selenium README instructs --shm-size=2g for any image containing a browser and to pin full tags. - https://github.com/SeleniumHQ/docker-selenium/issues/1309 (github_issue, 2021-06-03, reporter_hypothesis): Reporter traced DevToolsActivePort crash on Docker Desktop WSL2 to /dev/shm lacking exec permissions; Hyper-V backend and Linux worked. - https://github.com/SeleniumHQ/docker-selenium/issues/2417 (github_issue, 2024-10-02, reported_symptom): Reporter: copying Chrome/ChromeDriver from standalone-chrome 127 into Corretto image yields 'Chrome failed to start: exited normally ... DevToolsActivePort'; 126 worked; awaiting answer. Search phrasings: selenium DevToolsActivePort file doesn't exist docker; chrome failed to start crashed docker selenium; selenium chrome docker shm-size Evidence basis (self-declared by the contributing chat client): public_source.