Can not access through RDP upon after activating the Docker on Windows Server 2016

[Cengiz Ilerler]

ref: http://serverfault.com/questions/821626/can-not-access-through-rdp-upon-after-activating-the-docker-on-windows-server-20

I have a brand new Microsoft Windows Server 2016 v1607 (OS Build 14393.576) on Google Cloud Platform.

I connected to machine through RDP and installed only Containers feature then ran commands below as article here describes.

Install-Module -Name DockerMsftProvider -Repository PSGallery -Force

Install-Package -Name docker -ProviderName DockerMsftProvider

Restart-Computer -Force

WARNING I did not install none of the Hyper-V features

After the restart, I connected again through RDP and couldn't be able to run Computer Management, Task Manager etc. but did be able to open Command Prompt, Power Shell, Windows Explorer.

when I type docker version in Powershell result was

Client:
 Version:      1.12.2-cs2-ws-beta
 API version:  1.25
 Go version:   go1.7.1
 Git commit:   050b611
 Built:        Tue Oct 11 02:35:40 2016
 OS/Arch:      windows/amd64
error during connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.25/version: open //./pipe/docker_engine: The system cannot find the file specified.

Then I restarted the machine and can no longer be able to connect to the machine through RDP.

I have done this scenario twice and both ended with same result.

Please advise.

UPDATE I just tested on Microsoft Azure Platform server version is exactly same. docker version returns exactly same Client information. Looks like only difference is it can also return Server values.

Client:
 Version:      1.12.2-cs2-ws-beta
 API version:  1.25
 Go version:   go1.7.1
 Git commit:   050b611
 Built:        Tue Oct 11 02:35:40 2016
 OS/Arch:      windows/amd64

Server:
 Version:      1.12.2-cs2-ws-beta
 API version:  1.25
 Go version:   go1.7.1
 Git commit:   050b611
 Built:        Tue Oct 11 02:35:40 2016
 OS/Arch:      windows/amd64

[Faizan (Google Cloud Support)]

Hello Cengiz,

Our engineering team is already aware of this issue. To resolve the issue you need to run the following commands prior to installation of Docker:

netsh netkvm setparam 0 *RscIPv4 0

netsh netkvm restart 0

The detailed steps to install Docker on GCE Windows Server 2016 image are documented on this link[1]. 

For your current VM you can try to run the above mentioned commands using interactive serial console[2] and than reboot to see if the fixes the issue.

I hope that helps.

Faizan

[1] https://cloud.google.com/compute/docs/containers/#docker_on_windows

[2] https://cloud.google.com/compute/docs/instances/interacting-with-serial-console