[🐛 Bug]: Fly.io

[Adilmrqureshi]

What happened?

I started a selenium stand alone (selenium) server in fly.io using the docker container. However, when I send requests to the url the test are stuck in the queue and are not run.

How can we reproduce the issue?

Create a folder with a dockerfile in it with the following contents: 

FROM selenium/standalone-edge:latest
WORKDIR /app

Then run fly launch, which will launch the docker container to fly.io.

Then make a connect to the server remotely programmatically. I do did so via the following code: 

$serverUrl = env('SELENIUM_URL', false);
$driver = RemoteWebDriver::create($serverUrl, DesiredCapabilities::chrome());
$driver->get('[any website of choice]');
$text = $driver->findElement(WebDriverBy::tagName('tbody'))->getText();

Relevant log output

n/a

Operating System

Windows 11

Selenium version

selenium/standalone-chrome (image)

What are the browser(s) and version(s) where you see this issue?

chrome

What are the browser driver(s) and version(s) where you see this issue?

chrome

Are you using Selenium Grid?

4.23.0

[github-actions]

@Adilmrqureshi, thank you for creating this issue. We will troubleshoot it as soon as we can.

---

Info for maintainers

Triage this issue by using labels.

If information is missing, add a helpful comment and then I-issue-template label.

If the issue is a question, add the I-question label.

If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted label.

If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C), add the applicable G-* label, and it will provide the correct link and auto-close the issue.

After troubleshooting the issue, please add the R-awaiting answer label.

Thank you!

[joerg1985]

@Adilmrqureshi you are trying to run a chrome session inside a edge container. Therefore there is no matching free slot and the session does stay in the que until the timeout is hit.

@diemol do you think it does make sense to set the reject-unsupported-caps for the standalone server? There should no new nodes register to the server, so these sessions could be instantly rejected.

[diemol]

I created a PR for this. I will be available in the next Docker Selenium release.

Thanks for triaging, @joerg1985!

[github-actions]

This issue has been automatically locked since there has not been any recent activity since it was closed. Please open a new issue for related bugs.