-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
[🐛 Bug]: node-chrome and node-edge can no longer be used by buildx to create image for linux/arm64 environments #2276
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@garth-gross, thank you for creating this issue. We will troubleshoot it as soon as we can. Info for maintainersTriage this issue by using labels.
If information is missing, add a helpful comment and then
If the issue is a question, add the
If the issue is valid but there is no time to troubleshoot it, consider adding the
If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C),
add the applicable
After troubleshooting the issue, please add the Thank you! |
So looking further into this, v124.0 of Output from command:
I am guessing that #2266 "fixed" this bug, and I see that Is there another option for |
Hi @garth-gross, I am also surprise when reading this statement
Since only linux/amd64 images were published to Regarding |
Hi @VietND96,
This does work when I tried it. I am able to build the image and a smoke test of some of our automation, on a M3 MacBook Pro using Docker Desktop, using the built images completed without issue. I appreciate the solution provided and it gives us a additional point of discussion moving forward. I think this ticket can be closed as there isn't anything that needs to be done; it was just a misunderstanding of what was happening before the latest changes. Thank you again for providing the additional information. |
💬 Please ask questions at:
|
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
What happened?
For over a year we have been using docker's
buildx
functionality to buildlinux/amd64
andlinux/arm64
images from theselenium/node-chrome
andselenium/node-edge
docker images as there was additional functionality that we needed to add to the base image.Up until version 125.0 we had no problems creating images, but once the
125.0
image was released, we are now getting the following error during the build process:Attached is a proof of failure that mimics the process we are using
Duplication:
Pre-Reqs:
- Docker installed (confirmed failing on both Mac Docker Desktop and Ubuntu 22.04 Docker versions.)
cd
into the extracted directoryResult: Build fails with error:
Expected: Build completes
Additional notes about
selenium-pof.zip
:This configuration is used to be able to build images that might have slight tweaks to them (like base OS, different version numbers, different base images with the same steps applied).
docker-bake.hcl
is where most of the logic is contained. Specific line to care about:Dockerfile
used the build the images livesDockerfile
. Theqa-browsers-base
value is used by theDockerfile
to determine the image to build from.Dockerfile
:docker-bake.hcl
line 51 to be the following, the images will build properly:Dockerfile
used by the build process is located in theselenium-pof/qa/qa-browsers
directory. It leverages theqa-browsers-base
andplatforms
items defined indocker-bake.hcl
to determine the image and platforms to build for.Other things to note:
I can't pull the image on a M3 MacBook Pro. Running:
Yields:
Command used to start Selenium Grid with Docker (or Kubernetes)
Relevant log output
Operating System
Ubuntu 22.04
Docker Selenium version (image tag)
node-chrome:125.0
Selenium Grid chart version (chart version)
No response
The text was updated successfully, but these errors were encountered: