VM not created in Hyper-V about for-win HOT 12 CLOSED

I just installed the latest beta and it solves my issue as well. Thank you very much for fixing this.

from for-win.

Network debug

From starting the resource monitor(resmon.exe) I have the following things:

I can see that the Docker for Windows application is attempting to do something that involves it contacting a remote endpoint. The last image reveals the target of this traffic, but I have not been able to figure out what it is yet.

from for-win.

(X-post from https://forums.docker.com/t/docker-for-windows-does-not-start-after-reinstall)
I have tried to keep it running for 8 hours since last start. It seems like this is due to some timeout error. The updated log can be seen here: http://pastebin.com/qkK9tefv. Note that there is an 8 hour delay between getting a diagnostic ID and the next event. The thing that I am seeing as the possible culprit is this message Failed to upload an event and will retry later. This corresponds with the network activity I am reporting in the Github issue. Maybe a firewall issue?
The current status is that the Docker for Windows client shows up in the tray. It is however stuck with status "Docker is starting" and no updates to the log. With regards to network activity I am seeing the same activity as earlier reported. The biggest change is that I have established contact to the docker service with docker ps and that I can start a container with docker run busybox. I will try to see if I can reproduce this behaviour tomorrow.

from for-win.

I have found that the following makes Docker start:

1. Start Docker for Windows
2. Put computer to sleep for about 8 hours
3. Start computer again
4. Docker will now start up and it is possible to connect to the service, but the tray says Docker is runnig
5. Put computer to sleep for about 8 hours
6. Start computer again
7. Docker now runs as expected

This heavily indicates some timeout issue.

from for-win.

I'm a little confused about what the issue is here: The initial report is about Windows 10 pro build 10586 (or 1511 release) and the logs form the third comment suggest this is for Windows 10 Pro build 14393 (or 1607 release). Furthermore, the logs in the third comment suggest that the application started fine.

Also, if you have an issue, could you please use the Upload diagnostic... in the Diagnose and Feedback and quote the ID reported. That way we get additional diagnostics which may help finding the issue.

from for-win.

I updated the Windows version between the first and the second comment in order to see if that solved the issue. It did not.
With regards to the log in the third comment. Look at the difference in time between line 12 and 13. The As I mentioned in comment number 4 Docker only starts after a number of hours. During those hours the application attempts to send the seemingly same request to the same address without getting a response.

I am unable to use the "Upload diagnostic"-option in the application as part of the problem is that the application does not appear in the tray.

from for-win.

I have an easy workaround for this problem so users seeing this issue can run Docker 'stable' on Windows 1607.

1. Install Docker 'stable'
2. Ensure the checkbox on the last screen is checked so that Docker is launched after the install.
3. You will not see the Docker tray, but if you look at Task Manager, "Docker for Windows.exe" is running.
4. Pull out your network cable
5. Docker tray appears and initializes. You will see the Docker welcome screen.
6. Plug your network cable back in.

This appears to be an issue in Mixpanel Analytics running hanging for a long period of time on Windows 1607.

from for-win.

I can confirm that fix proposed by dsperling works with a wireless adapter as well. All you have to do is go into your adapters and enable/disable a couple of times.

@dsperling: The issue is also present in an earlier version of Windows, namely the one mentioned in the original comment.

from for-win.

@PetaPetaPeta @dsperling thanks for the update/details. We will release a Beta22 on the beta channel shortly (hopefully sometime today) and it has some improvements to the mixpanel code. Since we can easily reproduce the issue you are seeing it would be great if you could give the new Beta a try once it is out and report back. If the issue is still there we'll look into it more.

Thanks

from for-win.

@rneugeba looks like Beta 22 fixes this issue on my PC.

Note: This was tested with 1607 + the Cumulative Update for 1607 (KB3176495) which was released August 10.

from for-win.

Closing as the Beta22 seems to fix the issue. Note that Beat23 is out, but, unfortunately, due to a bug in the autoupdater, requires manual installation from https://download.docker.com/win/beta/InstallDocker.msi

from for-win.

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked

from for-win.