[🐛 Bug]: Running via Laravel Dusk crashes completely Docker

[riabiy-denis]

What happened?

I'm using intel mac 16 inch.
After upgrading to MacOS Ventura it just started to crash docker, when I try to use Laravel Dusk.

For some odd reason selenium/standalone-chrome-debug:3.12.0-cobalt don't crash, but just cant render everything properly 🤷🏻‍♂️

I had to try various old and not very options. 3.12.0-cobalt is the most recent that works for me now...for some reason. No other changes were made, but the upgrade.

Latest beta doesn't help.

Command used to start Selenium Grid with Docker

# For more information: https://laravel.com/docs/sail
version: "3"
services:
    #...
    selenium:
        image: "selenium/standalone-chrome:beta"
        volumes:
            - "/dev/shm:/dev/shm"
        ports:
            - "${FORWARD_SELENIUM_VNC_PORT:-5900}:5900"
        networks:
            - sail
networks:
    sail:
        driver: bridge

Relevant log output

2022-10-29 18:03:11,950 INFO Included extra file "/etc/supervisor/conf.d/selenium.conf" during parsing
2022-10-29 18:03:11,957 INFO RPC interface 'supervisor' initialized
2022-10-29 18:03:11,958 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2022-10-29 18:03:11,958 INFO supervisord started with pid 8
2022-10-29 18:03:12,962 INFO spawned: 'xvfb' with pid 10
2022-10-29 18:03:12,965 INFO spawned: 'vnc' with pid 11
2022-10-29 18:03:12,967 INFO spawned: 'novnc' with pid 12
2022-10-29 18:03:12,973 INFO spawned: 'selenium-standalone' with pid 16
Setting up SE_NODE_GRID_URL...
2022-10-29 18:03:12,986 INFO success: xvfb entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2022-10-29 18:03:12,987 INFO success: vnc entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2022-10-29 18:03:12,987 INFO success: novnc entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2022-10-29 18:03:12,987 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": "107.0", "platformName": "Linux"}'
max-sessions = 1

Starting Selenium Grid Standalone...
18:03:14.709 INFO [LoggingOptions.configureLogEncoding] - Using the system default encoding
18:03:14.718 INFO [OpenTelemetryTracer.createTracer] - Using OpenTelemetry for tracing
18:03:15.893 INFO [NodeOptions.getSessionFactories] - Detected 6 available processors
18:03:15.955 INFO [NodeOptions.report] - Adding chrome for {"browserVersion": "107.0","se:noVncPort": 7900,"browserName": "chrome","platformName": "LINUX","se:vncEnabled": true} 1 times
18:03:15.980 INFO [Node.<init>] - Binding additional locator mechanisms: name, relative, id
18:03:16.003 INFO [GridModel.setAvailability] - Switching Node 69496161-2a23-4a73-808e-8b65bd5a7fe3 (uri: http://172.18.0.4:4444) from DOWN to UP
18:03:16.004 INFO [LocalDistributor.add] - Added node 69496161-2a23-4a73-808e-8b65bd5a7fe3 at http://172.18.0.4:4444. Health check every 120s
18:03:16.302 INFO [Standalone.execute] - Started Selenium Standalone 4.5.3 (revision 4b786a1e430): http://172.18.0.4:4444
18:06:15.547 INFO [LocalDistributor.newSession] - Session request received by the Distributor: 
 [Capabilities {browserName: chrome, chromeOptions: {args: [--start-maximized]}, platform: ANY}, Capabilities {browserName: chrome, goog:chromeOptions: {args: [--start-maximized]}}]
Starting ChromeDriver 107.0.5304.62 (1eec40d3a5764881c92085aaee66d25075c159aa-refs/branch-heads/5304@{#942}) on port 26548
Only local connections are allowed.
Please see https://chromedriver.chromium.org/security-considerations for suggestions on keeping ChromeDriver safe.
[1667066775.632][SEVERE]: bind() failed: Cannot assign requested address (99)
ChromeDriver was started successfully.
18:06:17.153 WARN [ProtocolHandshake.createSession] - Support for Legacy Capabilities is deprecated; You are sending the following invalid capabilities: [chromeOptions, platform]; Please update to W3C Syntax: https://www.selenium.dev/blog/2022/legacy-protocol-support/
18:06:17.169 INFO [LocalNode.newSession] - Session created by the Node. Id: 45b3d5d0ae17f3892f4b45e4e752261a, Caps: Capabilities {acceptInsecureCerts: false, browserName: chrome, browserVersion: 107.0.5304.68, chrome: {chromedriverVersion: 107.0.5304.62 (1eec40d3a576..., userDataDir: /tmp/.com.google.Chrome.QWvkLL}, goog:chromeOptions: {debuggerAddress: localhost:43873}, networkConnectionEnabled: false, pageLoadStrategy: normal, platformName: ANY, proxy: Proxy(), se:cdp: http://localhost:43873, se:cdpVersion: 107.0.5304.68, se:vncEnabled: true, se:vncLocalAddress: ws://172.18.0.4:7900, setWindowRect: true, strictFileInteractability: false, timeouts: {implicit: 0, pageLoad: 300000, script: 30000}, unhandledPromptBehavior: dismiss and notify, webauthn:extension:credBlob: true, webauthn:extension:largeBlob: true, webauthn:virtualAuthenticators: true}
18:06:17.177 INFO [LocalDistributor.newSession] - Session created by the Distributor. Id: 45b3d5d0ae17f3892f4b45e4e752261a 
 Caps: Capabilities {acceptInsecureCerts: false, browserName: chrome, browserVersion: 107.0.5304.68, chrome: {chromedriverVersion: 107.0.5304.62 (1eec40d3a576..., userDataDir: /tmp/.com.google.Chrome.QWvkLL}, chromeOptions: {args: [--start-maximized]}, goog:chromeOptions: {debuggerAddress: localhost:43873}, networkConnectionEnabled: false, pageLoadStrategy: normal, platform: ANY, platformName: ANY, proxy: Proxy(), se:bidiEnabled: false, se:cdp: ws://172.18.0.4:4444/sessio..., se:cdpVersion: 107.0.5304.68, se:vnc: ws://172.18.0.4:4444/sessio..., se:vncEnabled: true, se:vncLocalAddress: ws://172.18.0.4:7900, setWindowRect: true, strictFileInteractability: false, timeouts: {implicit: 0, pageLoad: 300000, script: 30000}, unhandledPromptBehavior: dismiss and notify, webauthn:extension:credBlob: true, webauthn:extension:largeBlob: true, webauthn:virtualAuthenticators: true}
Trapped SIGTERM/SIGINT/x so shutting down supervisord...
2022-10-29 18:06:20,137 INFO exited: xvfb (terminated by SIGTERM; not expected)
2022-10-29 18:06:20,137 INFO exited: vnc (terminated by SIGTERM; not expected)
2022-10-29 18:06:20,137 INFO exited: novnc (terminated by SIGTERM; not expected)
2022-10-29 18:06:20,137 INFO exited: selenium-standalone (terminated by SIGTERM; not expected)
2022-10-29 18:06:20,137 WARN received SIGTERM indicating exit request
Unrecognized input header: 99

Operating System

macOS Ventura

Docker Selenium version (tag)

106 (actually, any has this issue for me)

[diemol]

What do you mean by "crashes"? I do not see anything special in the logs.

[riabiy-denis]

@diemol

What do you mean by "crashes"? I do not see anything special in the logs.

I meant literally. In the logs I've sent the whole tail. After that -> the whole Docker is down without any pop-up or whatever. All the containers and everything. Not gracefully. In a state of a constant reload (that animation of containers in the menu bar).

Then I have to restart it, it crashes and only after start again to bring it up.

I don't think I'm able to attach a screencast, but, if it's required -> I'm willing to. I really don't quite get what's going on with those reproducible crashes. It could be something obvious I'm just not noticing.

One of the things I did right away is cleaned my SSD and re-allocated resources for Docker. Still no luck.

[riabiy-denis]

@diemol

docker/for-mac#6530

This is the issue I'm experiencing. Looks it's not only me.

[yakobe]

Me too

[diemol]

Thanks for the information, seems this issue is not related to docker-selenium.

[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.