Merge pull request #240 from vania-pooh/master

Added documentation on starting Selenoid under Windows (fixes #239)
aerokube · Oct 13, 2017 · 2bd9df7 · 2bd9df7
2 parents b8f0c62 + 98999d4
commit 2bd9df7
Show file tree

Hide file tree

Showing 2 changed files with 10 additions and 0 deletions.
diff --git a/docs/index.adoc b/docs/index.adoc
@@ -26,6 +26,7 @@ include::logging-configuration-file.adoc[leveloffset=+1]
 include::timezone.adoc[leveloffset=+1]
 include::reloading-configuration.adoc[leveloffset=+1]
 include::docker-compose.adoc[leveloffset=+1]
+include::windows.adoc[leveloffset=+1]
 include::cli-flags.adoc[leveloffset=+1]
 
 == Advanced Features

diff --git a/docs/windows.adoc b/docs/windows.adoc
@@ -0,0 +1,9 @@
+== Selenoid under Windows
+
+While we normally recommend to start Selenoid using http://aerokube.com/cm/latest[Configuration Manager], it is possible to start it under Windows manually. The main difference from Unix operating systems is how volumes are mounted. In any Windows paths back slashes (`\`) should be replaced by forward slashes (`/`) and drive letter should be lower cased. For example for `C:\Users\admin` we get `c:/Users/admin`. So assuming that configuration file is located at `C:\selenoid` a typical startup command can look like: 
+
+    > docker run -d --name selenoid -v //var/run/docker.sock:/var/run/docker.sock -p 4444:4444 -v c:/selenoid:/etc/selenoid:ro aerokube/selenoid:latest-release
+
+The most strange part here is `-v //var/run/docker.sock:/var/run/docker.sock` but this is how (with two forward slashes) Docker socket should be mounted in Docker for Windows.
+
+