Could not start a new session. No nodes support the capabilities in the request

[ChloeSartorelli]

Preliminary checklist

• I am using the latest stable version of DDEV
• I am using the latest stable version of this add-on

Expected Behavior

I should be able to start a session and run my tests

Actual Behavior

When trying to start a session, I get a SessionNotCreated exception.
The error is

WebDriver\Exception\SessionNotCreated: Could not start a new session. No nodes support the capabilities in the request 
      Host info: host: '4fa062471d5f', ip: '172.23.0.3'
      Build info: version: '4.34.0', revision: '2a4c61c498'
      System info: os.name: 'Linux', os.arch: 'amd64', os.version: '6.12.10-76061203-generic', java.version: '21.0.8'
      Driver info: driver.version: unknown in vendor/instaclick/php-webdriver/lib/WebDriver/Exception.php:198

click to see full stack trace

#0 vendor/instaclick/php-webdriver/lib/WebDriver/AbstractWebDriver.php(179): WebDriver\Exception::factory()
      #1 vendor/instaclick/php-webdriver/lib/WebDriver/WebDriver.php(66): WebDriver\AbstractWebDriver->curl()
      #2 vendor/behat/mink-selenium2-driver/src/Selenium2Driver.php(335): WebDriver\WebDriver->session()
      #3 features/bootstrap/FeatureContext.php(32): Behat\Mink\Driver\Selenium2Driver->start()
      #4 vendor/behat/behat/src/Behat/Testwork/Call/Handler/RuntimeCallHandler.php(102): FeatureContext->iSeeInTheElement()
      #5 vendor/behat/behat/src/Behat/Testwork/Call/Handler/RuntimeCallHandler.php(58): Behat\Testwork\Call\Handler\RuntimeCallHandler->executeCall()
      #6 vendor/behat/behat/src/Behat/Testwork/Call/CallCenter.php(124): Behat\Testwork\Call\Handler\RuntimeCallHandler->handleCall()
      #7 vendor/behat/behat/src/Behat/Testwork/Call/CallCenter.php(86): Behat\Testwork\Call\CallCenter->handleCall()
      #8 vendor/behat/behat/src/Behat/Behat/Tester/Runtime/RuntimeStepTester.php(118): Behat\Testwork\Call\CallCenter->makeCall()
      #9 vendor/behat/behat/src/Behat/Behat/Tester/Runtime/RuntimeStepTester.php(66): Behat\Behat\Tester\Runtime\RuntimeStepTester->testDefinition()
      #10 vendor/behat/behat/src/Behat/Behat/Hook/Tester/HookableStepTester.php(65): Behat\Behat\Tester\Runtime\RuntimeStepTester->test()
      #11 vendor/behat/behat/src/Behat/Behat/EventDispatcher/Tester/EventDispatchingStepTester.php(66): Behat\Behat\Hook\Tester\HookableStepTester->test()
      #12 vendor/behat/behat/src/Behat/Behat/Tester/StepContainerTester.php(54): Behat\Behat\EventDispatcher\Tester\EventDispatchingStepTester->test()
      #13 vendor/behat/behat/src/Behat/Behat/Tester/Runtime/RuntimeScenarioTester.php(67): Behat\Behat\Tester\StepContainerTester->test()
      #14 vendor/behat/behat/src/Behat/Behat/Hook/Tester/HookableScenarioTester.php(65): Behat\Behat\Tester\Runtime\RuntimeScenarioTester->test()
      #15 vendor/behat/behat/src/Behat/Behat/EventDispatcher/Tester/EventDispatchingScenarioTester.php(97): Behat\Behat\Hook\Tester\HookableScenarioTester->test()
      #16 vendor/behat/behat/src/Behat/Behat/Tester/Runtime/IsolatingScenarioTester.php(60): Behat\Behat\EventDispatcher\Tester\EventDispatchingScenarioTester->test()
      #17 vendor/behat/behat/src/Behat/Behat/Tester/Runtime/RuntimeFeatureTester.php(70): Behat\Behat\Tester\Runtime\IsolatingScenarioTester->test()
      #18 vendor/behat/behat/src/Behat/Behat/Hook/Tester/HookableFeatureTester.php(68): Behat\Behat\Tester\Runtime\RuntimeFeatureTester->test()
      #19 vendor/behat/behat/src/Behat/Behat/EventDispatcher/Tester/EventDispatchingFeatureTester.php(69): Behat\Behat\Hook\Tester\HookableFeatureTester->test()
      #20 vendor/behat/behat/src/Behat/Testwork/Tester/Runtime/RuntimeSuiteTester.php(61): Behat\Behat\EventDispatcher\Tester\EventDispatchingFeatureTester->test()
      #21 vendor/behat/behat/src/Behat/Testwork/Hook/Tester/HookableSuiteTester.php(70): Behat\Testwork\Tester\Runtime\RuntimeSuiteTester->test()
      #22 vendor/behat/behat/src/Behat/Testwork/EventDispatcher/Tester/EventDispatchingSuiteTester.php(71): Behat\Testwork\Hook\Tester\HookableSuiteTester->test()
      #23 vendor/behat/behat/src/Behat/Testwork/Tester/Runtime/RuntimeExercise.php(68): Behat\Testwork\EventDispatcher\Tester\EventDispatchingSuiteTester->test()
      #24 vendor/behat/behat/src/Behat/Testwork/EventDispatcher/Tester/EventDispatchingExercise.php(69): Behat\Testwork\Tester\Runtime\RuntimeExercise->test()
      #25 vendor/behat/behat/src/Behat/Testwork/Ordering/OrderedExercise.php(66): Behat\Testwork\EventDispatcher\Tester\EventDispatchingExercise->test()
      #26 vendor/behat/behat/src/Behat/Testwork/Tester/Cli/ExerciseController.php(165): Behat\Testwork\Ordering\OrderedExercise->test()
      #27 vendor/behat/behat/src/Behat/Testwork/Tester/Cli/ExerciseController.php(114): Behat\Testwork\Tester\Cli\ExerciseController->testSpecifications()
      #28 vendor/behat/behat/src/Behat/Testwork/Cli/Command.php(63): Behat\Testwork\Tester\Cli\ExerciseController->execute()
      #29 vendor/symfony/console/Command/Command.php(318): Behat\Testwork\Cli\Command->execute()
      #30 vendor/symfony/console/Application.php(1074): Symfony\Component\Console\Command\Command->run()
      #31 vendor/symfony/console/Application.php(341): Symfony\Component\Console\Application->doRunCommand()
      #32 vendor/behat/behat/src/Behat/Testwork/Cli/Application.php(139): Symfony\Component\Console\Application->doRun()
      #33 vendor/symfony/console/Application.php(192): Behat\Testwork\Cli\Application->doRun()
      #34 vendor/behat/behat/bin/behat(34): Symfony\Component\Console\Application->run()
      #35 vendor/bin/behat(119): include('...')
      #36 {main}

Steps To Reproduce

1. clone https://github.com/GuySartorelli/ddev-selenium-issue-example and change to that directory
2. run ddev start
3. run ddev composer install
4. run ddev exec vendor/bin/behat -vvv

Anything else?

I got the error in a more sophisticated setup than the one above, which had previously been working (say, a month ago or so).
I have created the setup in "steps to reproduce" as a toy example to show the error.

[ChloeSartorelli]

I'm guessing this is related to whatever's causing the tests to fail just based on the timing

[weitzman]

Those tests are now fixed. I dont think they were related to your issue but you could fetch rc2 and see.

[ChloeSartorelli]

Thanks for that. Tried 2.0.0-rc2 and you're right, that didn't solve it

[sensespidey]

FWIW, I'm seeing this same error on a fresh install today, running version 2.1.1 of the add-on, and ddev v1.24.10. I'm primarily using behat for testing, but have narrowed down the issue to the chromedriver image that gets pulled in. If I make the following change to docker-compose.selenium-chrome.yaml immediately after installing the add-on, my javascript behat tests go from complaining with the error reported here to working perfectly again:

-    image: selenium/standalone-chromium:138.0
+    image: seleniarm/standalone-chromium:4.1.4-20220429

Is there a way to specify the image used in the install command, or can this be specified in the config.selenium-standalone-chrome.yaml?

[rachellawson]

Yes, I’m seeing the same.

[mxr576]

Behat support has just became official in 2.2.0, could you please try it out and report back with your findings? Thanks in advance

https://github.com/ddev/ddev-selenium-standalone-chrome/releases/tag/2.2.0

[heathstannard]

Seeing this same issue - even at v2.2.0.

Reverting to seleniarm/standalone-chromium:4.1.4-20220429 functions but the browser version is too old for my tests. I have tried adjusting the capabilities but no go so far.

[mxr576]

Maybe you should try v1 on 2.3.0, if you could find time for this, please also report back about your results. Thanks!

https://github.com/ddev/ddev-selenium-standalone-chrome#drupal-version-compatibility

[heathstannard]

I ended up tracking this down to the use of the instaclick/php-webdriver package. Switching out https://github.com/minkphp/MinkSelenium2Driver for https://github.com/Lullabot/MinkSelenium2Driver (and therefore https://github.com/Lullabot/php-webdriver ) resolved my issues with v2 / D11.3 / Drupal Test Traits.

[mxr576]

Thanks for getting back with important details. Yes, switching to Lullabot's fork is the way to go and those should work well with this addon.