Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Object reference not set to an instance of an object when starting docker for windows #464
I installed Docker onto my computer but got a blue screen after the installation. (Due to an unrelated problem where I can't create HyperV VHD's on my C Drive due to a Bios NVME driver).
I created a symlink for the c:\users.....docker\machine\machines folder to another drive which would solve the issue of the blue screen.
However when I now start Docker for Windows.exe I only see the following error:
Additional information you deem important (e.g. issue happens only occasionally):
I already tried reinstalling docker and Hyper-V without any luck. I also tried manually creating a new VM with the following command:
However this didn't solve the issue.
Also running any commands with docker run give errors. E.g.:
Additional environment details (AWS, VirtualBox, physical, etc.):
referenced this issue
Feb 4, 2017
I'm seeing the same issue. I confirmed that the 'com.docker.service' does show RUNNING. I sent a crash report (Diag ID: 83E0204E-E01B-4DEA-ABAB-726BE7C306C9/2017-02-22_16-29-13). Screenshot of the message and the log.txt below
I was also getting Blue Screen at boot for a while until I disabled Docker for Win as a Startup item. Not sure if that's related or not because if I manually start it a little later I don't get the Blue Screens anymore, just the error message from Docker for Win