Docker: [windows] improve error thrown when attempting to connect to Docker when Docker isn't running : IDEA-268618
![Support mapped named pipe endpoint for Windows container · Issue #1179 · portainer/portainer · GitHub Support mapped named pipe endpoint for Windows container · Issue #1179 · portainer/portainer · GitHub](https://user-images.githubusercontent.com/12378390/51519376-0dcb3800-1e36-11e9-958d-6461cab51c39.png)
Support mapped named pipe endpoint for Windows container · Issue #1179 · portainer/portainer · GitHub
![Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? – IDEs Support (IntelliJ Platform) | JetBrains Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? – IDEs Support (IntelliJ Platform) | JetBrains](https://intellij-support.jetbrains.com/hc/user_images/XgjjqrTATN1YAkz45bhniQ.jpeg)
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? – IDEs Support (IntelliJ Platform) | JetBrains
![Troubleshoot Docker EE on Windows Server 2016 (“HNS Failed with error: …”) | by Ashish Singh Baghel | Medium Troubleshoot Docker EE on Windows Server 2016 (“HNS Failed with error: …”) | by Ashish Singh Baghel | Medium](https://miro.medium.com/v2/resize:fit:886/1*01oQIGZDueyB3AKMBN1G-A.png)
Troubleshoot Docker EE on Windows Server 2016 (“HNS Failed with error: …”) | by Ashish Singh Baghel | Medium
![Sitecore login redirects to http instead of https after we added 'hostname' attributes in docker-compose.yml - Sitecore Stack Exchange Sitecore login redirects to http instead of https after we added 'hostname' attributes in docker-compose.yml - Sitecore Stack Exchange](https://i.stack.imgur.com/JsK1L.png)
Sitecore login redirects to http instead of https after we added 'hostname' attributes in docker-compose.yml - Sitecore Stack Exchange
![Support mapped named pipe endpoint for Windows container · Issue #1179 · portainer/portainer · GitHub Support mapped named pipe endpoint for Windows container · Issue #1179 · portainer/portainer · GitHub](https://user-images.githubusercontent.com/207759/30248409-93beed50-9627-11e7-85d3-3ca9417959bd.png)
Support mapped named pipe endpoint for Windows container · Issue #1179 · portainer/portainer · GitHub
![Docker WSL context does not start when docker start (At logon at least, probably always) · Issue #4404 · docker/for-win · GitHub Docker WSL context does not start when docker start (At logon at least, probably always) · Issue #4404 · docker/for-win · GitHub](https://user-images.githubusercontent.com/2266487/62411007-17f09f00-b5ee-11e9-9a01-7c5585e7b8a7.png)
Docker WSL context does not start when docker start (At logon at least, probably always) · Issue #4404 · docker/for-win · GitHub
![pipe/docker_engine: Access is denied. In the default daemon configuration on Windows, the docker client must be run elevated to connect · Issue #1679 · docker/for-win · GitHub pipe/docker_engine: Access is denied. In the default daemon configuration on Windows, the docker client must be run elevated to connect · Issue #1679 · docker/for-win · GitHub](https://user-images.githubusercontent.com/164266/36010914-9c911082-0d5c-11e8-9213-98f349f082fb.png)
pipe/docker_engine: Access is denied. In the default daemon configuration on Windows, the docker client must be run elevated to connect · Issue #1679 · docker/for-win · GitHub
![docker - Connect to docker_engine (named pipe) from a C# Service Fabric app on Windows - Stack Overflow docker - Connect to docker_engine (named pipe) from a C# Service Fabric app on Windows - Stack Overflow](https://i.stack.imgur.com/j27W2.png)