When a container or driver is started (ping is successful) Selenoid does a new session request just in the same way as standard Selenium client.ĭepending on what is returned as response on the previous step session is marked as created or failed. This is done by sending HEAD requests to the port. Before proceeding to next step Selenoid waits for required port to be open. All requests during startup are marked as pending. When there is a free slot for request Selenoid decides whether a Docker container or standalone driver process should be created. Queued requests just block and continue to wait. When requests reach the limit - subsequent requests are placed in queue. Selenoid -limit flag specifies how many sessions can be created simultaneously. Running Selenoid in custom Docker networkĪ new session request arrives to Selenoid. Running Selenoid in default Docker network Syncing Browser Images from Existing File Specifying Capabilities via Protocol Extensions Links to Application Containers: applicationContainers Video Recording: enableVideo, videoName, videoScreenSize, videoFrameRate, videoCodec Custom Screen Resolution: screenResolution
