Up until late last year I was experimenting with Docker container on Windows 10 and Server 2016 using the Experimental version of Docker. Well things took a turn for the worst and basically Docker refused to run and kept crashing. Life being as it is I went onto other things and have only just come back to Docker and installing the release stable version (17.03.0-ce-win1 (10296)) I get this when switching from Linux containers to Windows:-
Docker daemon failed with message:
time="2017-03-02T17:10:44Z" level=warning msg="Running experimental build"
time="2017-03-02T17:10:44.990632000Z" level=debug msg="Listener created for HTTP on npipe (//./pipe/docker_engine_windows)"
time="2017-03-02T17:10:44.995133700Z" level=info msg="Windows default isolation mode: hyperv"
time="2017-03-02T17:10:44.995133700Z" level=debug msg="Using default logging driver json-file"
time="2017-03-02T17:10:44.995632900Z" level=debug msg="WindowsGraphDriver InitFilter at C:\\ProgramData\\Docker\\windowsfilter"
time="2017-03-02T17:10:44.995632900Z" level=debug msg="Using graph driver windowsfilter"
time="2017-03-02T17:10:44.995632900Z" level=debug msg="Max Concurrent Downloads: 3"
time="2017-03-02T17:10:44.995632900Z" level=debug msg="Max Concurrent Uploads: 5"
time="2017-03-02T17:10:45.018215100Z" level=info msg="Graph migration to content-addressability took 0.00 seconds"
….LOTS MORE OF THE MESSAGE HERE…
time="2017-03-02T17:10:45.551683600Z" level=debug msg="start clean shutdown of all containers with a 15 seconds timeout..."
Error starting daemon: Error initializing network controller: Error creating default network: HNS failed with error : The parameter is incorrect.
at Docker.Backend.ContainerEngine.Windows.DoStart(Settings settings)
at Docker.Backend.ContainerEngine.Windows.Restart(Settings settings)
at Docker.Core.Pipe.NamedPipeServer.<>c__DisplayClass8_0.<Register>b__0(Object parameters)
at Docker.Core.Pipe.NamedPipeServer.RunAction(String action, Object parameters)
To fix this I stopped the MobyLinux VM that was running via Hyper-V Manager and did a factory reset on the Docker daemon.
It did the reset and now runs Windows containers, so if anybody has the same issue try replicating this.