search

seleniumhq-community / docker-seleniarm

Multi-Arch (arm64/armhf/amd64) Docker images for the Selenium Grid Server
https://hub.docker.com/u/seleniarm
Other
249 stars 26 forks source link

[🐛 Bug]: the quick start results in a container with no browser #38

Closed mitchmeyer1 closed 1 year ago

mitchmeyer1 commented 1 year ago

What happened?

OSX Ventura 13.0 (22A8380) MacBook Pro 2023 Apple M2 Max

I killed all my services and containers, and i pruned all of my docker resources so there are no images, volumes etc...

I then ran through the QUICK START instructions.

localhost:4444 points to a UI dashboard, not a virtual browser i can point my tests to

Optional step 4 localhost:7900 goes to my linux desktop, however in the applications folder of the linux system there is no browser. My rspec tests also cannot connect to any browser. I dont see any evidence there is a browser anywhere, just a linux system.

I am porting over from an intel chip running selenium/standalone-firefox:latest. On this system, if you right click on the desktop you can open a firefox browser in the applications fire. Or if you go into bash in the linux system, you can open firefox from there. Both of these techniques on seleniarm fail.

Command used to start Selenium Grid with Docker

just used the Quick Start Command:
docker run -d -p 4444:4444 -p 7900:7900 --shm-size="2g" selenium/standalone-firefox:4.9.1-20230508

Relevant log output

No log output

Operating System

MacOS Ventura

Docker Selenium version (tag)

seleniarm/standalone-firefox:latest

diemol commented 1 year ago

You are not using the seleniarm images, have you checked https://github.com/seleniumhq-community/docker-seleniarm#running-the-arm-container-images?

mitchmeyer1 commented 1 year ago

@diemol sorry pasted the wrong version, corrected it: seleniarm/standalone-firefox:latest

mitchmeyer1 commented 1 year ago

it works now - im not sure what i did wrong but gonna close this out, thanks for looking at it

github-actions[bot] commented 7 months ago

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.