-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[🐛 Bug]: running selenium/standalone-chrome as user 1000 #2142
Comments
@rob-bankers, 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! |
|
Issue solved by using 1200:1201 user and group. |
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?
Hi,
The selenium/standalone-chrome, which used to run with user 1000 and group 1000, is no longer functional in release 1.20.0. It now requires initiation with user 1200 and group 1201. Is this intentional?
This is still working:
docker run --user 1200:1201 \ selenium/standalone-chrome:120.0
Command used to start Selenium Grid with Docker (or Kubernetes)
Relevant log output
Operating System
MacOS Rancher Desktop
Docker Selenium version (image tag)
selenium/standalone-chrome:121.0
Selenium Grid chart version (chart version)
No response
The text was updated successfully, but these errors were encountered: