Chainguard Container for selenium-node-firefox

Chainguard Containers are regularly-updated, secure-by-default container images.

Download this Container Image

For those with access, this container image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/selenium-node-firefox:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

Components

Docker Selenium has multiple components which can act as standalone docker images

1. base
2. hub
3. node-docker
4. node-base
5. node-chromium
6. node-firefox
7. standalone
8. standalone-docker
9. standalone-chromium
10. standalone-firefox
11. event-bus
12. distributor
13. router
14. session-queue
15. sessions

Usage

Run the container with the following command:

docker run --shm-size="2g" -p 4444:4444 -p 7900:7900 cgr.dev/chainguard/docker-selenium-standalone-chromium:latest

Verify Selenium is running:

curl -sL http://localhost:4444/status` should return a `200` status code, and the response body should contain `{"value":{"ready":true}}` with 1 `availability: UP` node.

Access Selenium:

http://localhost:4444

Access noVNC:

http://localhost:7900/vnc.html`:

• Login with the password secret.

Any WebDriver tests should point to Selenium on on port 4444.

The following is an example ChromeDriver test using Selenium to retrieve Chainguard's homepage:

from selenium import webdriver
from time import sleep

print("Testing ChromeDriver...")

options = webdriver.ChromeOptions()

driver = webdriver.Remote(
  command_executor='http://localhost:4444/',
  options=options
)

'''Maximize window'''
driver.maximize_window()
sleep(5)

'''Retrieve Chainguards homepage'''
driver.get("https://www.chainguard.dev/")
sleep(5)

'''Exit'''
driver.close()
driver.quit()
print("ChromeDriver test successful!")

Please note that Chromium is ran in a headless state with the sandbox with GPU access disabled with the flags:

--headless --no-sandbox --disable-gpu

Chromium is ran headless with GPU access disabled as the container does not have GPU access.

Chromium's sandbox has been disabled as the container is sandboxed from the host environment, and because the container is running as the root user.

This can be overridden via the environment variable CHROMIUM_USER_FLAGS though this is unsupported.

Running multiple components

All of the Docker Selenium components can be deployed together using using kubernetes with helm. More documentation on helm deployment is ava

Add Helm Repo

helm repo add docker-selenium https://www.selenium.dev/docker-selenium

To use them, simply replace the appropriate image: path with the Chainguard specific Jaeger image. Below is an example values file for doing this with helm: Microsoft Edge is disabled as it is not one of the offered Chainguard images

global:
  imageRegistry: cgr.dev/<ORGANIZATION>
isolateComponents:
  enabled: true
nodeChrome:
  imageName: docker-selenium-node-chromium
  imageTag: latest
edgeNode:
  enabled: false
router:
  imageName: docker-selenium-router
  imageTag: latest
distribution:
  imageName: docker-selenium-distributor
  imageTag: latest
sessionMap:
  imageName: docker-selenium-sessions
  imageTag: latest
sessionQueue:
  imageName: docker-selenium-session-queue
  imageTag: latest
eventBus:
  imageName: docker-selenium-event-bus
  imageTag: latest
jaeger:
  allInOne:
    enabled: true
    image:
      repository: cgr.dev/ORGANISATION/jaeger-all-in-one
      tag: latest

Install Helm Chart

helm upgrade --install selenium-grid charts/selenium-grid \
  --values values.yaml

What are Chainguard Containers?

Chainguard's free tier of Starter container images are built with Wolfi, our minimal Linux undistro.

All other Chainguard Containers are built with Chainguard OS, Chainguard's minimal Linux operating system designed to produce container images that meet the requirements of a more secure software supply chain.

The main features of Chainguard Containers include:

• Minimal design, without unnecessary software bloat
• Daily builds to ensure container images are up-to-date with available security patches
• High quality build-time SBOMs attesting to the provenance of all artifacts within the image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a development, or -dev, variant.

In all other cases, including Chainguard Containers tagged as :latest or with a specific version number, the container images include only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager.

Although the -dev container image variants have similar security features as their more minimal versions, they include additional software that is typically not necessary in production environments. We recommend using multi-stage builds to copy artifacts from the -dev variant into a more minimal production image.

Need additional packages?

To improve security, Chainguard Containers include only essential dependencies. Need more packages? Chainguard customers can use Custom Assembly to add packages, either through the Console, chainctl, or API.

To use Custom Assembly in the Chainguard Console: navigate to the image you'd like to customize in your Organization's list of images, and click on the Customize image button at the top of the page.

Learn More

Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.

Trademarks

This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.