-
-
Couldn't load subscription status.
- Fork 2.6k
Closed
Labels
Description
What happened?
The amd64 and arm64 builds of "node-firefox" appear to be using different Firefox versions for the same tag.
For example, when leveraging selenium/node-firefox:130.0 the on an x64 machine; the resulting version in Selenium Hub is 130.0 as expected. Unforutnately, when using this same tag on arm64; the resulting version is actually 132.0.
I noticed when attempting to update to 132.0 tag the amd64 updates properly but the arm64 version is actually 134.0.
Command used to start Selenium Grid with Docker (or Kubernetes)
services:
selenium:
container_name: selenium
image: selenium/hub:4.19
ports:
- 4442:4442
- 4443:4443
- 4444:4444
healthcheck:
disable: true
selenium-node:
container_name: selenium-firefox
image: selenium/node-firefox:130.0
ports:
- 50001:7900
environment:
- SE_EVENT_BUS_HOST=selenium
- SE_EVENT_BUS_PUBLISH_PORT=4442
- SE_EVENT_BUS_SUBSCRIBE_PORT=4443
shm_size: 2gb
depends_on:
- selenium
healthcheck:
disable: trueRelevant log output
Will Attach Screenshots after ticket creation.Operating System
Linux, MacOSX
Docker Selenium version (image tag)
4.19
Selenium Grid chart version (chart version)
No response