You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Hub/README.md
-17Lines changed: 0 additions & 17 deletions
Original file line number
Diff line number
Diff line change
@@ -26,23 +26,6 @@ Selenium has the support of some of the largest browser vendors who have taken (
26
26
27
27
See the Selenium [site](http://docs.seleniumhq.org/) for documation on usage within your test code.
28
28
29
-
## Known Issues
30
-
31
-
### Problems with `/dev/random`
32
-
33
-
You may occasionally see that nodes will not immediately connect with the hub. In some cases the delay has been as high as 40 minutes. This is due to a known problem with linux containers where there is a lack of entropy within the running container. [James Bayer](http://blog.pivotal.io/cloud-foundry-pivotal/features/challenges-with-randomness-in-multi-tenant-linux-container-platforms) wrote a great article explaining the core of the problem.
34
-
35
-
36
-
You can either install an entropy gathering daemon (EGD), such as [HAVEGED](http://www.issihosts.com/haveged/index.html), on you docker host.
37
-
38
-
-- or --
39
-
40
-
Run your container with the `-v /dev/urandom:/dev/random` option. ie:
41
-
42
-
```
43
-
$ docker run -d -v /dev/urandom:/dev/random --link selenium-hub:hub selenium/node-firefox
44
-
```
45
-
46
29
## License
47
30
48
31
View [license information](https://code.google.com/p/selenium/source/browse/COPYING) for the software contained in this image.
Copy file name to clipboardExpand all lines: NodeBase/README.md
-17Lines changed: 0 additions & 17 deletions
Original file line number
Diff line number
Diff line change
@@ -27,23 +27,6 @@ Selenium has the support of some of the largest browser vendors who have taken (
27
27
28
28
See the Selenium [site](http://docs.seleniumhq.org/) for documation on usage within your test code.
29
29
30
-
## Known Issues
31
-
32
-
### Problems with `/dev/random`
33
-
34
-
You may occasionally see that nodes will not immediately connect with the hub. In some cases the delay has been as high as 40 minutes. This is due to a known problem with linux containers where there is a lack of entropy within the running container. [James Bayer](http://blog.pivotal.io/cloud-foundry-pivotal/features/challenges-with-randomness-in-multi-tenant-linux-container-platforms) wrote a great article explaining the core of the problem.
35
-
36
-
37
-
You can either install an entropy gathering daemon (EGD), such as [HAVEGED](http://www.issihosts.com/haveged/index.html), on you docker host.
38
-
39
-
-- or --
40
-
41
-
Run your container with the `-v /dev/urandom:/dev/random` option. ie:
42
-
43
-
```
44
-
$ docker run -d -v /dev/urandom:/dev/random --link selenium-hub:hub selenium/node-firefox
45
-
```
46
-
47
30
## License
48
31
49
32
View [license information](https://code.google.com/p/selenium/source/browse/COPYING) for the software contained in this image.
Copy file name to clipboardExpand all lines: NodeChrome/README.md
-17Lines changed: 0 additions & 17 deletions
Original file line number
Diff line number
Diff line change
@@ -27,23 +27,6 @@ Selenium has the support of some of the largest browser vendors who have taken (
27
27
28
28
See the Selenium [site](http://docs.seleniumhq.org/) for documation on usage within your test code.
29
29
30
-
## Known Issues
31
-
32
-
### Problems with `/dev/random`
33
-
34
-
You may occasionally see that nodes will not immediately connect with the hub. In some cases the delay has been as high as 40 minutes. This is due to a known problem with linux containers where there is a lack of entropy within the running container. [James Bayer](http://blog.pivotal.io/cloud-foundry-pivotal/features/challenges-with-randomness-in-multi-tenant-linux-container-platforms) wrote a great article explaining the core of the problem.
35
-
36
-
37
-
You can either install an entropy gathering daemon (EGD), such as [HAVEGED](http://www.issihosts.com/haveged/index.html), on you docker host.
38
-
39
-
-- or --
40
-
41
-
Run your container with the `-v /dev/urandom:/dev/random` option. ie:
42
-
43
-
```
44
-
$ docker run -d -v /dev/urandom:/dev/random --link selenium-hub:hub selenium/node-firefox
45
-
```
46
-
47
30
## License
48
31
49
32
View [license information](https://code.google.com/p/selenium/source/browse/COPYING) for the software contained in this image.
Copy file name to clipboardExpand all lines: NodeChromeDebug/README.md
-17Lines changed: 0 additions & 17 deletions
Original file line number
Diff line number
Diff line change
@@ -50,23 +50,6 @@ Selenium has the support of some of the largest browser vendors who have taken (
50
50
51
51
See the Selenium [site](http://docs.seleniumhq.org/) for documation on usage within your test code.
52
52
53
-
## Known Issues
54
-
55
-
### Problems with `/dev/random`
56
-
57
-
You may occasionally see that nodes will not immediately connect with the hub. In some cases the delay has been as high as 40 minutes. This is due to a known problem with linux containers where there is a lack of entropy within the running container. [James Bayer](http://blog.pivotal.io/cloud-foundry-pivotal/features/challenges-with-randomness-in-multi-tenant-linux-container-platforms) wrote a great article explaining the core of the problem.
58
-
59
-
60
-
You can either install an entropy gathering daemon (EGD), such as [HAVEGED](http://www.issihosts.com/haveged/index.html), on you docker host.
61
-
62
-
-- or --
63
-
64
-
Run your container with the `-v /dev/urandom:/dev/random` option. ie:
65
-
66
-
```
67
-
$ docker run -d -v /dev/urandom:/dev/random --link selenium-hub:hub selenium/node-firefox
68
-
```
69
-
70
53
## License
71
54
72
55
View [license information](https://code.google.com/p/selenium/source/browse/COPYING) for the software contained in this image.
Copy file name to clipboardExpand all lines: NodeDebug/README.template.md
-17Lines changed: 0 additions & 17 deletions
Original file line number
Diff line number
Diff line change
@@ -50,23 +50,6 @@ Selenium has the support of some of the largest browser vendors who have taken (
50
50
51
51
See the Selenium [site](http://docs.seleniumhq.org/) for documation on usage within your test code.
52
52
53
-
## Known Issues
54
-
55
-
### Problems with `/dev/random`
56
-
57
-
You may occasionally see that nodes will not immediately connect with the hub. In some cases the delay has been as high as 40 minutes. This is due to a known problem with linux containers where there is a lack of entropy within the running container. [James Bayer](http://blog.pivotal.io/cloud-foundry-pivotal/features/challenges-with-randomness-in-multi-tenant-linux-container-platforms) wrote a great article explaining the core of the problem.
58
-
59
-
60
-
You can either install an entropy gathering daemon (EGD), such as [HAVEGED](http://www.issihosts.com/haveged/index.html), on you docker host.
61
-
62
-
-- or --
63
-
64
-
Run your container with the `-v /dev/urandom:/dev/random` option. ie:
65
-
66
-
```
67
-
$ docker run -d -v /dev/urandom:/dev/random --link selenium-hub:hub selenium/node-firefox
68
-
```
69
-
70
53
## License
71
54
72
55
View [license information](https://code.google.com/p/selenium/source/browse/COPYING) for the software contained in this image.
Copy file name to clipboardExpand all lines: NodeFirefox/README.md
-17Lines changed: 0 additions & 17 deletions
Original file line number
Diff line number
Diff line change
@@ -27,23 +27,6 @@ Selenium has the support of some of the largest browser vendors who have taken (
27
27
28
28
See the Selenium [site](http://docs.seleniumhq.org/) for documation on usage within your test code.
29
29
30
-
## Known Issues
31
-
32
-
### Problems with `/dev/random`
33
-
34
-
You may occasionally see that nodes will not immediately connect with the hub. In some cases the delay has been as high as 40 minutes. This is due to a known problem with linux containers where there is a lack of entropy within the running container. [James Bayer](http://blog.pivotal.io/cloud-foundry-pivotal/features/challenges-with-randomness-in-multi-tenant-linux-container-platforms) wrote a great article explaining the core of the problem.
35
-
36
-
37
-
You can either install an entropy gathering daemon (EGD), such as [HAVEGED](http://www.issihosts.com/haveged/index.html), on you docker host.
38
-
39
-
-- or --
40
-
41
-
Run your container with the `-v /dev/urandom:/dev/random` option. ie:
42
-
43
-
```
44
-
$ docker run -d -v /dev/urandom:/dev/random --link selenium-hub:hub selenium/node-firefox
45
-
```
46
-
47
30
## License
48
31
49
32
View [license information](https://code.google.com/p/selenium/source/browse/COPYING) for the software contained in this image.
Copy file name to clipboardExpand all lines: NodeFirefoxDebug/README.md
-17Lines changed: 0 additions & 17 deletions
Original file line number
Diff line number
Diff line change
@@ -50,23 +50,6 @@ Selenium has the support of some of the largest browser vendors who have taken (
50
50
51
51
See the Selenium [site](http://docs.seleniumhq.org/) for documation on usage within your test code.
52
52
53
-
## Known Issues
54
-
55
-
### Problems with `/dev/random`
56
-
57
-
You may occasionally see that nodes will not immediately connect with the hub. In some cases the delay has been as high as 40 minutes. This is due to a known problem with linux containers where there is a lack of entropy within the running container. [James Bayer](http://blog.pivotal.io/cloud-foundry-pivotal/features/challenges-with-randomness-in-multi-tenant-linux-container-platforms) wrote a great article explaining the core of the problem.
58
-
59
-
60
-
You can either install an entropy gathering daemon (EGD), such as [HAVEGED](http://www.issihosts.com/haveged/index.html), on you docker host.
61
-
62
-
-- or --
63
-
64
-
Run your container with the `-v /dev/urandom:/dev/random` option. ie:
65
-
66
-
```
67
-
$ docker run -d -v /dev/urandom:/dev/random --link selenium-hub:hub selenium/node-firefox
68
-
```
69
-
70
53
## License
71
54
72
55
View [license information](https://code.google.com/p/selenium/source/browse/COPYING) for the software contained in this image.
Copy file name to clipboardExpand all lines: README.md
-17Lines changed: 0 additions & 17 deletions
Original file line number
Diff line number
Diff line change
@@ -114,23 +114,6 @@ When you are prompted for the password it is __secret__. If you wish to change t
114
114
RUN x11vnc -storepasswd <your-password-here> /home/seluser/.vnc/passwd
115
115
```
116
116
117
-
## Known Issues
118
-
119
-
### Problems with `/dev/random`
120
-
121
-
You may occasionally see that nodes will not immediately connect with the hub. In some cases the delay has been as high as 40 minutes. This is due to a known problem with linux containers where there is a lack of entropy within the running container. [James Bayer](http://blog.pivotal.io/cloud-foundry-pivotal/features/challenges-with-randomness-in-multi-tenant-linux-container-platforms) wrote a great article explaining the core of the problem.
122
-
123
-
124
-
You can either install an entropy gathering daemon (EGD), such as [HAVEGED](http://www.issihosts.com/haveged/index.html), on you docker host.
125
-
126
-
-- or --
127
-
128
-
Run your container with the `-v /dev/urandom:/dev/random` option. ie:
129
-
130
-
```
131
-
$ docker run -d -v /dev/urandom:/dev/random --link selenium-hub:hub selenium/node-firefox
Copy file name to clipboardExpand all lines: Standalone/README.template.md
-16Lines changed: 0 additions & 16 deletions
Original file line number
Diff line number
Diff line change
@@ -28,22 +28,6 @@ Selenium has the support of some of the largest browser vendors who have taken (
28
28
29
29
See the Selenium [site](http://docs.seleniumhq.org/) for documation on usage within your test code.
30
30
31
-
## Known Issues
32
-
33
-
### Problems with `/dev/random`
34
-
35
-
You may occasionally see that Selenium containers are not immediately responsive. In some cases the delay has been as high as 40 minutes. This is due to a known problem with linux containers where there is a lack of entropy within the running container. [James Bayer](http://blog.pivotal.io/cloud-foundry-pivotal/features/challenges-with-randomness-in-multi-tenant-linux-container-platforms) wrote a great article explaining the core of the problem.
36
-
37
-
You can either install an entropy gathering daemon (EGD), such as [HAVEGED](http://www.issihosts.com/haveged/index.html), on you docker host.
38
-
39
-
-- or --
40
-
41
-
Run your container with the `-v /dev/urandom:/dev/random` option. ie:
42
-
43
-
```
44
-
$ docker run -d -v /dev/urandom:/dev/random selenium/standalone-##BROWSER_LC##
45
-
```
46
-
47
31
## License
48
32
49
33
View [license information](https://code.google.com/p/selenium/source/browse/COPYING) for the software contained in this image.
Copy file name to clipboardExpand all lines: StandaloneChrome/README.md
-16Lines changed: 0 additions & 16 deletions
Original file line number
Diff line number
Diff line change
@@ -28,22 +28,6 @@ Selenium has the support of some of the largest browser vendors who have taken (
28
28
29
29
See the Selenium [site](http://docs.seleniumhq.org/) for documation on usage within your test code.
30
30
31
-
## Known Issues
32
-
33
-
### Problems with `/dev/random`
34
-
35
-
You may occasionally see that Selenium containers are not immediately responsive. In some cases the delay has been as high as 40 minutes. This is due to a known problem with linux containers where there is a lack of entropy within the running container. [James Bayer](http://blog.pivotal.io/cloud-foundry-pivotal/features/challenges-with-randomness-in-multi-tenant-linux-container-platforms) wrote a great article explaining the core of the problem.
36
-
37
-
You can either install an entropy gathering daemon (EGD), such as [HAVEGED](http://www.issihosts.com/haveged/index.html), on you docker host.
38
-
39
-
-- or --
40
-
41
-
Run your container with the `-v /dev/urandom:/dev/random` option. ie:
42
-
43
-
```
44
-
$ docker run -d -v /dev/urandom:/dev/random selenium/standalone-chrome
45
-
```
46
-
47
31
## License
48
32
49
33
View [license information](https://code.google.com/p/selenium/source/browse/COPYING) for the software contained in this image.
Copy file name to clipboardExpand all lines: StandaloneFirefox/README.md
-16Lines changed: 0 additions & 16 deletions
Original file line number
Diff line number
Diff line change
@@ -28,22 +28,6 @@ Selenium has the support of some of the largest browser vendors who have taken (
28
28
29
29
See the Selenium [site](http://docs.seleniumhq.org/) for documation on usage within your test code.
30
30
31
-
## Known Issues
32
-
33
-
### Problems with `/dev/random`
34
-
35
-
You may occasionally see that Selenium containers are not immediately responsive. In some cases the delay has been as high as 40 minutes. This is due to a known problem with linux containers where there is a lack of entropy within the running container. [James Bayer](http://blog.pivotal.io/cloud-foundry-pivotal/features/challenges-with-randomness-in-multi-tenant-linux-container-platforms) wrote a great article explaining the core of the problem.
36
-
37
-
You can either install an entropy gathering daemon (EGD), such as [HAVEGED](http://www.issihosts.com/haveged/index.html), on you docker host.
38
-
39
-
-- or --
40
-
41
-
Run your container with the `-v /dev/urandom:/dev/random` option. ie:
42
-
43
-
```
44
-
$ docker run -d -v /dev/urandom:/dev/random selenium/standalone-firefox
45
-
```
46
-
47
31
## License
48
32
49
33
View [license information](https://code.google.com/p/selenium/source/browse/COPYING) for the software contained in this image.
0 commit comments