<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Grid on Selenium</title><link>https://deploy-preview-2615--selenium-dev.netlify.app/categories/grid/</link><description>Recent content in Grid on Selenium</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 14 Apr 2026 07:37:58 +0700</lastBuildDate><atom:link href="https://deploy-preview-2615--selenium-dev.netlify.app/categories/grid/index.xml" rel="self" type="application/rss+xml"/><item><title>Selenium Grid Docker Images Are Now Mirrored to GHCR</title><link>https://deploy-preview-2615--selenium-dev.netlify.app/blog/2026/selenium-grid-docker-images-are-now-mirrored-to-ghcr/</link><pubDate>Sat, 04 Apr 2026 00:00:00 +0000</pubDate><guid>https://deploy-preview-2615--selenium-dev.netlify.app/blog/2026/selenium-grid-docker-images-are-now-mirrored-to-ghcr/</guid><description>&lt;p>The request started with a simple question in &lt;a href="https://github.com/SeleniumHQ/docker-selenium/issues/2939">issue #2939&lt;/a>: can we publish Selenium Grid Docker images to GitHub Container Registry as well as Docker Hub?&lt;/p>
&lt;p>The answer is now yes.&lt;/p>
&lt;p>Official Selenium Grid Docker images are now available from &lt;strong>GitHub Container Registry (GHCR)&lt;/strong> under:&lt;/p>
&lt;pre tabindex="0">&lt;code>ghcr.io/seleniumhq
&lt;/code>&lt;/pre>&lt;p>This is a mirror, not a replacement. Docker Hub remains available, and existing users do not need to change anything. But if your environment prefers GHCR, blocks Docker Hub, or simply wants another official source for the same images, you now have one.&lt;/p></description></item><item><title>HtmlUnit Remote: Acquiring Remote HtmlUnitDriver Session in Selenium 4 Grid</title><link>https://deploy-preview-2615--selenium-dev.netlify.app/blog/2024/htmlunit-remote-for-selenium-4-grid/</link><pubDate>Mon, 19 Aug 2024 00:00:00 +0000</pubDate><guid>https://deploy-preview-2615--selenium-dev.netlify.app/blog/2024/htmlunit-remote-for-selenium-4-grid/</guid><description>&lt;h1 id="htmlunit-remote">HTMLUNIT REMOTE&lt;/h1>
&lt;p>&lt;a href="https://central.sonatype.com/search?q=com.nordstrom.ui-tools&amp;#43;htmlunit-remote&amp;amp;core=gav">&lt;img src="https://img.shields.io/maven-central/v/com.nordstrom.ui-tools/htmlunit-remote.svg" alt="Maven Central">&lt;/a>&lt;/p>
&lt;p>The &lt;a href="https://github.com/seleniumhq-community/htmlunit-remote">HtmlUnit Remote&lt;/a> project implements a &lt;a href="https://www.w3.org/TR/webdriver2">W3C WebDriver protocol&lt;/a> wrapper for &lt;a href="https://github.com/SeleniumHQ/htmlunit-driver">HtmlUnitDriver&lt;/a>, which enables &lt;strong>Selenium 4 Grid&lt;/strong> to supply remote sessions of this headless browser.&lt;/p>
&lt;h3 id="background">Background&lt;/h3>
&lt;p>To eliminate behavioral differences between local and remote configurations, the &lt;a href="https://github.com/sbabcoc/Selenium-Foundation">Selenium Foundation&lt;/a> framework always acquires browser sessions from a &lt;strong>Grid&lt;/strong> instance, managing its own local grid instance when not configured to use an existing grid. &lt;strong>Selenium 3 Grid&lt;/strong> could be configured to supply &lt;strong>HtmlUnitDriver&lt;/strong> sessions, supported by special-case handling within the Node server itself. This handling was not carried over into &lt;strong>Selenium 4 Grid&lt;/strong>, which was completely re-engineered with new architecture and vastly expanded capabilities.&lt;/p></description></item></channel></rss>