Public | Automated Build

Last pushed: 5 days ago
Short Description
Short description is empty for this repo.
Full Description

Selenium Grid Standalone - Chrome

Selenium Standalone Server with Chrome

Dockerfile

selenium/standalone-chrome Dockerfile

How to use this image

$ docker run -d -P selenium/standalone-chrome

You can acquire the port that Selenium is listening on by running:

$ docker port <container-name|container-id> 4444
#=> 0.0.0.0:49338

What is Selenium?

Selenium automates browsers. That's it! What you do with that power is entirely up to you. Primarily, it is for automating web applications for testing purposes, but is certainly not limited to just that. Boring web-based administration tasks can (and should!) also be automated as well.

Selenium has the support of some of the largest browser vendors who have taken (or are taking) steps to make Selenium a native part of their browser. It is also the core technology in countless other browser automation tools, APIs and frameworks.

See the Selenium site for documation on usage within your test code.

License

View license information for the software contained in this image.

Getting Help

User Group

The first place where people ask for help about Selenium is the Official User Group. Here, you'll find that most of the time, someone already found the problem you are facing right now, and usually reached the solution for which you are looking.

Note: Please make sure to search the group before asking for something. Your question likely won't get answered if it was previously answered in another discussion!

Chat Room

The best place to ask for help is the user group (because they also keep the information accessible for others to read in the future). However, if you have a very important (or too simple) issue that needs a solution ASAP, you can always enter the IRC chat room. You might just find someone ready to help on #selenium at Freenode.

Issues

If you have any problems with or questions about this image, please contact us through a Github issue. If you have any problems with or questions about Selenium, please contact us through Selenium's Bug Tracker.

Contributing

There are many ways to contribute whether by answering user questions, additional docs, or pull request we look forward to hearing from you.

If you do supply a patch we will need you to sign the CLA. We are part of SFC

Docker Pull Command
Owner
selenium
Source Repository

Comments (11)
dooflow
a month ago

I have problem when i change user-agent. When change it doesn't work. If I go to http://www.xhaus.com/headers it say same user-agent . If I change it with AddArgument("--user-agent='TESTING'"); ir doesn't change. But if i test it in local selenium it work ok. Only fail in this docker. Why?

reachbharathan
4 months ago

Can i use this image and run my test in a single docker image without initiating two containers?

abdulnasar
4 months ago

Yes, it even broke for me and I have to stick to my previous tag.

jeremycraigmartinez
4 months ago

Your guys' push today broke our ci because you renamed the chromedriver from chromedriver-2.29 to chromedriver-2.30. You need to specify this by name when instantiating selenium via the command line, so wouldn't it be better to keep a soft link here as chromedriver that points to the version specified executable? For consistency across future updates

fertavora
5 months ago

Hey Everyone!
I'm trying to use this docker to run some tests and I got this error:

session deleted because of page crash from tab crashed

Any idea what I can be missing? Thanks!

lastlink
5 months ago

leee
6 months ago

Can not display Chinese properly

droyster
10 months ago

the default user is seluser. What is the default password?

mhamann
2 years ago

@mcowan: chrome-standalone runs on its own, whereas chrome-node needs a Selenium grid server to "own" it.

@bdew70: The process on the container itself runs on 4444 but that's exposed to the host via a port assigned by the Docker runtime. So you can run as many of these as you want (within reason).

bdew70
2 years ago

Is there a way to run more than 1 of these containers in order run multiple tests at once? I assume that since the container runs on 127.0.0.1:4444 there will be conflict among multiple containers.