Object reference not set to an instance of an object when starting docker for windows #464

Closed
devedse opened this Issue Feb 4, 2017 · 14 comments

Comments

Projects
None yet
5 participants
@devedse

devedse commented Feb 4, 2017

Description

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:

image

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:
docker-machine create --driver hyperv vm

However this didn't solve the issue.

Also running any commands with docker run give errors. E.g.:

C:\Users\Davy>docker pull hello-world
Using default tag: latest
Warning: failed to get default registry endpoint from daemon (error during connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.25/info: open //./pipe/docker_engine: The system cannot find the file specified. In the default daemon configuration on Windows, the docker client must be run elevated to connect. This error may also indicate that the docker daemon is not running.). Using system default: https://index.docker.io/v1/
error during connect: Post http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.25/images/create?fromImage=hello-world&tag=latest: open //./pipe/docker_engine: The system cannot find the file specified. In the default daemon configuration on Windows, the docker client must be run elevated to connect. This error may also indicate that the docker daemon is not running.

Output of docker version:

Client:
 Version:      1.13.0
 API version:  1.25
 Go version:   go1.7.3
 Git commit:   49bf474
 Built:        Wed Jan 18 16:20:26 2017
 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. In the default daemon configuration on Windows, the docker client must be run elevated to connect. This error may also indicate that the docker daemon is not running.

Output of docker info:

error during connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.25/info: open //./pipe/docker_engine: The system cannot find the file specified. In the default daemon configuration on Windows, the docker client must be run elevated to connect. This error may also indicate that the docker daemon is not running.

Additional environment details (AWS, VirtualBox, physical, etc.):
My enviroment is Windows 10 with Docker for Windows which I want to run in the linux VM.

@rn

This comment has been minimized.

Show comment
Hide comment
@rn

rn Feb 5, 2017

Member

@devedse With Docker for Windows you don't need to play with docker-machine. Just start the application and it will create thew Linux VM for you. There should be an icon in the systray

Member

rn commented Feb 5, 2017

@devedse With Docker for Windows you don't need to play with docker-machine. Just start the application and it will create thew Linux VM for you. There should be an icon in the systray

@devedse

This comment has been minimized.

Show comment
Hide comment
@devedse

devedse Feb 5, 2017

Hey meugeba, thanks for your advice, but as I described in my post, the issue is that I can't start the docker application. So no matter how bad I would like to do that, that is actually the main issue :).

devedse commented Feb 5, 2017

Hey meugeba, thanks for your advice, but as I described in my post, the issue is that I can't start the docker application. So no matter how bad I would like to do that, that is actually the main issue :).

@rn

This comment has been minimized.

Show comment
Hide comment
@rn

rn Feb 5, 2017

Member

can you send the crash report and report the Diagnostics ID?

Member

rn commented Feb 5, 2017

can you send the crash report and report the Diagnostics ID?

@devedse

This comment has been minimized.

Show comment
Hide comment
@devedse

devedse Feb 5, 2017

I uploaded the log as:
image

devedse commented Feb 5, 2017

I uploaded the log as:
image

@simonferquel

This comment has been minimized.

Show comment
Hide comment
@simonferquel

simonferquel Feb 6, 2017

@devedse can you try to remove everything in C:\Users<username>\AppData\Roaming\Docker ?

@devedse can you try to remove everything in C:\Users<username>\AppData\Roaming\Docker ?

@devedse

This comment has been minimized.

Show comment
Hide comment
@devedse

devedse Feb 9, 2017

Will check that out

devedse commented Feb 9, 2017

Will check that out

@rn

This comment has been minimized.

Show comment
Hide comment
@rn

rn Feb 14, 2017

Member

A few more pointers:

  • Could you send us a crash report/diagnostics and report the diagnostics ID here?
  • Could you check with Get-Service com.docker.service if the service is running?
Member

rn commented Feb 14, 2017

A few more pointers:

  • Could you send us a crash report/diagnostics and report the diagnostics ID here?
  • Could you check with Get-Service com.docker.service if the service is running?
@devedse

This comment has been minimized.

Show comment
Hide comment
@devedse

devedse Feb 15, 2017

rneugeba, I tried to do that but as you can see in the screenshot above the diagnostic id is unreadable.

I will have access to this machine next week again, so then I will continue my investigation.

devedse commented Feb 15, 2017

rneugeba, I tried to do that but as you can see in the screenshot above the diagnostic id is unreadable.

I will have access to this machine next week again, so then I will continue my investigation.

@rn

This comment has been minimized.

Show comment
Hide comment
@rn

rn Feb 16, 2017

Member

@devedse thanks for getting back

Member

rn commented Feb 16, 2017

@devedse thanks for getting back

@audioboxer217

This comment has been minimized.

Show comment
Hide comment
@audioboxer217

audioboxer217 Feb 22, 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

image

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

image

@audioboxer217

This comment has been minimized.

Show comment
Hide comment
@audioboxer217

audioboxer217 Feb 28, 2017

Somehow I missed @simonferquel's suggestion to remove everything from the AppData/Roaming folder. That resolved the issue for me.

audioboxer217 commented Feb 28, 2017

Somehow I missed @simonferquel's suggestion to remove everything from the AppData/Roaming folder. That resolved the issue for me.

@devedse

This comment has been minimized.

Show comment
Hide comment
@devedse

devedse Mar 3, 2017

Indeed removeing AppData/Roaming/Docker also solved this issue for me. I think the settings.json file in there was corrupted.

Maybe we need to change the code a little bit so that Docker is able to recover from corrupted settings files?

devedse commented Mar 3, 2017

Indeed removeing AppData/Roaming/Docker also solved this issue for me. I think the settings.json file in there was corrupted.

Maybe we need to change the code a little bit so that Docker is able to recover from corrupted settings files?

@rn

This comment has been minimized.

Show comment
Hide comment
@rn

rn Mar 3, 2017

Member

@devedse thanks for reporting back. There has been other reports of the settings file being corrupted here #455 and we have an internal issue tracking it. so I'm closing this issue.

Member

rn commented Mar 3, 2017

@devedse thanks for reporting back. There has been other reports of the settings file being corrupted here #455 and we have an internal issue tracking it. so I'm closing this issue.

@rn rn closed this Mar 3, 2017

@jayfresh

This comment has been minimized.

Show comment
Hide comment
@jayfresh

jayfresh Jun 8, 2017

Deleting AppData/Roaming/Docker worked for me too. 👍

jayfresh commented Jun 8, 2017

Deleting AppData/Roaming/Docker worked for me too. 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment